task-verification-pipeline

Anveio's avatarfrom Anveio

Run and debug a repo verification pipeline (`./verify.sh --ui=false` or equivalent), including stage selection and opt-in E2E tiers.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 17, 2025
[Testing and QA]

When & Why to Use This Skill

The Task Verification Pipeline skill automates the execution and debugging of repository-level verification workflows. It streamlines essential quality assurance tasks including linting, typechecking, unit testing, and building. By providing a standardized interface for running local verification scripts and managing opt-in E2E testing tiers, it helps developers identify and resolve CI failures quickly while maintaining high code standards.

Use Cases

  • Local CI Debugging: Reproduce and fix pipeline failures locally by running the exact verification stages used in continuous integration environments.
  • Targeted Quality Checks: Run specific verification stages such as '/verify-lint' or '/verify typecheck' to validate code changes incrementally without executing the full suite.
  • Configurable E2E Testing: Execute end-to-end test suites with selectable tiers (smoke, standard, or full) to ensure system stability before major releases.
  • Automated Refactoring: Utilize the '/lint-and-learn' command to automatically fix linting errors, extract architectural lessons, and generate pull requests in one workflow.
nametask-verification-pipeline
descriptionRun and debug a repo verification pipeline (`./verify.sh --ui=false` or equivalent), including stage selection and opt-in E2E tiers.

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

  1. Establish baseline (headless): ./verify.sh --ui=false
  2. If it fails, fix the failing stage and rerun until green.
  3. Only run E2E when needed: ./verify.sh --ui=false --e2e=standard

Key facts

  • E2E is opt-in; default verify skips it unless --e2e is 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.md or similar).
  • Your repo’s verification entrypoint (commonly verify.sh or a npm run verify script).