---
name: check
description: Run lint + PHPUnit in an isolated Docker container and get back a concise pass/fail summary. Use when the user asks to "run tests", "check the code", "lint", or wants to validate a change before committing. Delegates to a Haiku-powered container-tester subagent so the full test output stays out of the main conversation.
---

# /check — run lint + tests in a one-shot container

When this skill is invoked, **immediately** spawn the project's `container-tester` subagent via the Agent tool. Do not run `appctl check` yourself in the main session — the whole point of the skill is to keep verbose phpunit/build output out of the main context.

## How to invoke

```
Agent({
  description: "Run lint + tests in container",
  subagent_type: "container-tester",
  prompt: "Run `./appctl check` from the repo root. Report only failures and a one-line summary, per your output policy."
})
```

If the user passed an argument to the skill, route it:
- `/check lint` → prompt: `"Run `./appctl lint` only. Report per your output policy."`
- `/check test` → prompt: `"Run `./appctl test` only. Report per your output policy."`
- `/check <anything else>` → pass it through as additional context: `"Run `./appctl check`. Caller note: <argument>. Report per your output policy."`

## After the agent returns

Show the agent's reply to the user as-is. It is already shaped to be the final answer — don't add commentary, don't re-summarise, don't suggest fixes unless the user asks.

If the report indicates failures and the user follows up with "fix it" / "what's wrong" / similar, *then* take over with full investigation in the main session.
