From cogitation
Ensures verification commands are run before claiming success. Checks EC for project-specific gotchas. Use before asserting tests pass, builds succeed, or bugs are fixed.
npx claudepluginhub merewhiplash/engram-cogitator --plugin cogitationThis skill uses the workspace's default tool permissions.
Don't claim something works until you've seen the evidence.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Don't claim something works until you've seen the evidence.
Announce: "I'm using the verifying skill to confirm this works."
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION
Before running commands, get the configured commands from EC:
ec_search:
query: project config
type: config
area: project
Extract: test_command, lint_command, build_command
If no config: Use sensible defaults but warn:
"No project config found. Using default commands. Consider running @init."
Search EC for verification issues in this area:
ec_search:
query: verification gotcha
type: learning
Apply any known workarounds or warnings.
Before claiming any success:
Use the project-configured commands:
| Claim | Command | Fallback |
|---|---|---|
| "Tests pass" | {test_command} | npm test |
| "Build succeeds" | {build_command} | npm run build |
| "Types check" | {lint_command} | npx tsc --noEmit |
| "Lints clean" | {lint_command} | npm run lint |
| Claim | Requires | Not Sufficient |
|---|---|---|
| "Tests pass" | Test output showing 0 failures | Previous run, "should pass" |
| "Build succeeds" | Build with exit 0 | Linter passing |
| "Bug fixed" | Test for the bug passes | "I changed the code" |
| "Type-safe" | Type-check with no errors | "Looks right" |
Without fresh evidence, never say:
NO: "Fixed the bug, tests should pass now"
YES: [Run tests]
"Tests pass: 47/47. Bug fix verified."
If verification reveals a non-obvious issue:
ec_add:
type: learning
area: verification
content: [What the gotcha was]
rationale: Discovered during verification
Examples worth storing:
Evidence first. Claims second.