scaffold/.claude/skills/stop/SKILL.md
Generate a session-end summary that passes the stop hook on the first attempt
npx skillsauth add gstredny/lauren-loop stopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The stop hook (~/.claude/hooks/stop-require-summary.sh) blocks exit until your summary contains all 4 sections below. Each section is validated by a regex — your text must match the pattern or the hook rejects it.
Hook regex: \.(py|js|ts|jsx|tsx|go|rs|md|sh|json|yaml|yml|toml|css|html|vue|rb|java|kt|swift|c|cpp|h|hpp|sql|tf|hcl)\b
You MUST mention file extensions. The hook counts occurrences of dotted extensions.
executor.py — added intent field. Created SKILL.md — new stop skill."Hook regex: ([0-9]+ (pass|fail|test|error|skip|succeed)|[0-9]+/[0-9]+|passed.*failed|tests?:?\s*[0-9])
You MUST include numeric counts next to test keywords.
Hook regex: (what's left|remaining|next steps|left to do|todo|still need|left off|nothing.*(left|remain))
You MUST use one of the trigger phrases above.
Hook regex: (task file (updated|unchanged)|task file.*docs/tasks/open/.*\.md|no scope.*change|no criteria.*change)
You MUST declare whether the task file was updated or unchanged.
Copy and fill in:
**What changed:**
- Modified `<file>` — <what changed>
- Created `<file>` — <what changed>
**Test results:** <N> passed, <N> failed (or "No tests required — documentation-only change")
**What's left:** <next steps, or "Nothing remaining">
**Task file status:** Task file updated: docs/tasks/open/<name>.md (or "Task file unchanged — no scope/criteria changes")
| Mistake | Why it fails | Fix |
|---------|-------------|-----|
| "Updated the service" | No file extension | "Updated service.py" |
| "Tests pass" | No numbers | "560 passed, 0 failed" |
| "Will do X next time" | No trigger phrase | "What's left: X" |
| Omitting task file line | Missing section 4 | Add "Task file updated/unchanged" line |
development
Follow the end-to-end delivery workflow for planning, task-file management, execution, code review, verification, and closeout without relying on Claude-specific hooks or command conventions.
testing
Plan implementation work before coding by defining public interfaces, real collaborator boundaries, and vertical RED or VERIFY slices.
development
Manage task files in docs/tasks/open and docs/tasks/closed, including task discovery, resume/create rules, append-only Attempts logging, Left Off At updates, Code Review field handling, and needs verification closeout.
data-ai
Review an implementation plan before execution to catch missed success criteria, scope creep, constraint violations, unverified assumptions, and missed reuse opportunities.