Agent skill
task-verification-pipeline
Run and debug a repo verification pipeline (`./verify.sh --ui=false` or equivalent), including stage selection and opt-in E2E tiers.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/task-verification-pipeline
SKILL.md
Verification Pipeline
When to use
Use this when the task mentions:
./verify.sh, “verification pipeline”, “format/lint/typecheck/test/build”- CI failures or “why does verify fail”
- Enabling E2E (
--e2e=smoke|standard|full)
Default workflow
- Establish baseline (headless):
./verify.sh --ui=false - If it fails, fix the failing stage and rerun until green.
- Only run E2E when needed:
./verify.sh --ui=false --e2e=standard
Key facts
- E2E is opt-in; default verify skips it unless
--e2eis set. - Prefer root scripts (
npm run lint,npm run typecheck,npm run test,npm run build) for targeted iteration.
Slash Commands
Use these for accelerated workflows:
| Command | Purpose |
|---|---|
/verify |
Run full pipeline or specific stage (/verify lint) |
/verify-lint [package] |
Quick lint check with optional scope |
/lint-and-learn |
Auto-fix lint + extract lessons + create PR |
Canonical repo docs
- Your repo’s verification runner docs (commonly
apps/dev-tooling/README.mdor similar). - Your repo’s verification entrypoint (commonly
verify.shor anpm run verifyscript).
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?