Claude Skill

verify-done

Runs the comprehensive quality gate before declaring work done: discovers the checks CI actually runs, executes them in order, then reviews git status and the session diff. Use when the user says 'verify done' or '/verify-done', or before pushing any branch.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download domengabrovsek-claude-skills_verify-done-48da5d0.zip · 0 KB
Part of domengabrovsek/claude — 41 skills

Install

skills CLI npx skills add https://github.com/domengabrovsek/agent-config/tree/main/skills/verify-done
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install domengabrovsek-claude@llmmart
Git git clone https://github.com/domengabrovsek/agent-config.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole domengabrovsek/claude collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Comprehensive quality gate before declaring work done.

  1. Discover CI steps: read .github/workflows/*.yml (or .gitlab-ci.yml, Jenkinsfile, etc.) and package.json scripts to find the actual checks CI runs. Only run what CI actually runs - do not guess or add extra steps.
  2. Run each CI step in order: execute the discovered commands (lint, typecheck, test, build, etc.) in the same order as CI. Stop at the first failure.
  3. Git status: show uncommitted changes and untracked files.
  4. Diff review: summarize what changed in this session (files, lines added/removed).
  5. Spec check: if a spec in .claude/state/specs/ has branch: <current branch>, spawn the Spec Verifier and include its verdict. Any automated criterion not PASS at HEAD fails the gate.

If all CI steps pass and git status is clean: output "READY - all quality gates passed." If any step fails: list failures and stop. Do NOT declare work done. If no CI configuration is found, say so and ask the user what checks to run.

Files (claude)
  • SKILL.md 1.3 KB
    ---
    name: verify-done
    description: "Runs the comprehensive quality gate before declaring work done: discovers the checks CI actually runs, executes them in order, then reviews git status and the session diff. Use when the user says 'verify done' or '/verify-done', or before pushing any branch."
    ---
    
    Comprehensive quality gate before declaring work done.
    
    1. **Discover CI steps**: read `.github/workflows/*.yml` (or `.gitlab-ci.yml`, `Jenkinsfile`, etc.) and `package.json` scripts to find the actual checks CI runs. Only run what CI actually runs - do not guess or add extra steps.
    2. **Run each CI step in order**: execute the discovered commands (lint, typecheck, test, build, etc.) in the same order as CI. Stop at the first failure.
    3. **Git status**: show uncommitted changes and untracked files.
    4. **Diff review**: summarize what changed in this session (files, lines added/removed).
    5. **Spec check**: if a spec in `.claude/state/specs/` has `branch: <current branch>`, spawn the `Spec Verifier` and include its verdict. Any automated criterion not PASS at HEAD fails the gate.
    
    If all CI steps pass and git status is clean: output "READY - all quality gates passed."
    If any step fails: list failures and stop. Do NOT declare work done.
    If no CI configuration is found, say so and ask the user what checks to run.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related