mansi.kansara
2ee257c630
Wire debug-issue, verify-change, and explain-code into the universal resolver with reasons, extend AGENTS.md slash list, cross-link build Phase 3 and Phase 6, refresh generator goldens for three stacks, and note cross-skill links in the build skill design spec. Co-authored-by: Cursor <cursoragent@cursor.com>
74 lines
2.8 KiB
Cheetah
74 lines
2.8 KiB
Cheetah
---
|
|
name: Verify change
|
|
description: Post-change or pre-PR verification without the full /build lifecycle. Use /verify with optional scope; respects testing depth {{TESTING_DEPTH}} and E2E {{E2E_TOOL}}; no success claims without pasted outputs.
|
|
---
|
|
|
|
# Verify — {{PROJECT_NAME}}
|
|
|
|
Run a **focused** verification gate after a change or before a small PR — without replaying the entire `/build` document.
|
|
|
|
**Stack:** **{{STATE_MANAGEMENT}}** / **{{ARCHITECTURE}}** / **{{BACKEND}}** / {{PLATFORMS_LIST}}. **Testing depth:** {{TESTING_DEPTH}}. **E2E tool:** {{E2E_TOOL}}. **Codegen:** {{CODEGEN_LIST}}.
|
|
|
|
## Usage
|
|
|
|
```
|
|
/verify [optional scope: paths, “small PR”, or feature name]
|
|
```
|
|
|
|
**Examples:**
|
|
|
|
- `/verify lib/features/auth/`
|
|
- `/verify small PR before push`
|
|
- `/verify after dependency bump`
|
|
|
|
---
|
|
|
|
## Checklist (adapt to testing depth)
|
|
|
|
> **Invoke skill: `superpowers:verification-before-completion`**
|
|
|
|
**Do not claim success** until the user (or you, in a trusted environment) has pasted **real** output for each applicable item below.
|
|
|
|
### Always (typical Flutter repo)
|
|
|
|
- [ ] **Unit / widget tests** for touched code — e.g. `flutter test <path> --no-pub` or full suite as appropriate.
|
|
**Required in paste:** a line showing tests passed (or the exact failure to fix).
|
|
- [ ] **`flutter analyze`**
|
|
**Required in paste:** `No issues found!` or the analyzer errors to address.
|
|
|
|
### When `testing.depth` is `full` or `e2e` (this brief: **{{TESTING_DEPTH}}**)
|
|
|
|
- [ ] **Integration / E2E** — use **{{E2E_TOOL}}** patterns from `.cursor/rules/` (e.g. Patrol). Run on a device or emulator when scenarios require it; paste run output.
|
|
|
|
### When `testing.depth` is `unit_widget` only
|
|
|
|
- [ ] **Integration / device E2E** — *not* mandatory unless the change touches integration-only surfaces; if skipped, say so explicitly in the paste.
|
|
|
|
### Hooks and codegen
|
|
|
|
- [ ] **`lefthook run pre-commit`** — run when the repo has Lefthook configured (especially when **{{CODEGEN_LIST}}** is not `none`). Paste hook summary.
|
|
If hooks are not set up for this workspace, write *“skipped — hooks not configured”* instead of failing silently.
|
|
|
|
### CI alignment
|
|
|
|
- [ ] For **{{CICD_TOOL}}** ({{CICD_RAW}}): confirm the same commands the pipeline runs (analyze + tests) are green locally. Note flavor-scoped secrets for **{{FLAVORS_LIST}}**.
|
|
|
|
---
|
|
|
|
## ACTION REQUIRED — paste block
|
|
|
|
Print this table and wait for pasted output before declaring done:
|
|
|
|
```
|
|
VERIFICATION — paste real output for each line you executed:
|
|
|
|
[ ] flutter test … → (paste: pass count or failures)
|
|
[ ] flutter analyze → (paste: no issues or errors)
|
|
[ ] integration / e2e (if depth is full/e2e or change requires it) →
|
|
[ ] lefthook run pre-commit → (paste or "skipped — not configured")
|
|
```
|
|
|
|
If anything fails: switch to **`/debug`** with the failing log before guessing.
|
|
|
|
**Template version:** {{TEMPLATE_VERSION}}
|