Agent skill

Ensure Quality

by gambitph in gambitph/Stackable

Local quality gate for the current worktree: review for risk/correctness (break, leak, undo intent), standards, spec, and anti-slop; then test, document, lint.

GPL-3.0Auto-check passedTesting & QA

Install Ensure Quality

skills CLI
$ npx skills add gambitph/Stackable --skill ensure-quality -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install gambitph/Stackable ensure-quality --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/ensure-quality .claude/skills/ensure-quality && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ensure-quality
GitHub stars
350
Token cost
~1.5k tokens
SKILL.md length
707 words
Files
10
Skills in repo
18
Repo updated
First seen
Licence
GPL-3.0

At a glance

Local quality gate for the current worktree: review for risk/correctness (break, leak, undo intent), standards, spec, and anti-slop; then test, document, lint.

  • Works in 5 steps: Synthesize intent. Capture what the user… → Discover the project. Follow… → Pin the fixed point. Default: merge-base… → …
  • The user asks to ensure quality
  • SKILL.md covers When to run, Preconditions, Pipeline loop and Summary
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ensure Quality is an agent skill from gambitph/Stackable. Local quality gate for the current worktree: review for risk/correctness (break, leak, undo intent), standards, spec, and anti-slop; then test, document, lint. Mechanical one-liner auto-fix and HITL for ask-user findings; ship-readiness summary. Use when the user asks to ensure quality, run the quality gate, validate before commit, or gate changes; after finishing substantive or AI-generated code changes; and always before the agent commits.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files (for example `agents/openai.yaml`, `reference/anti-slop.md` and `reference/discover.md`).

It sits in Testing & QA, covering Quality gates, Humanizing AI text and Linting and formatting. The repository describes itself as: Page Builder Blocks for WordPress. An Amazing Block Library for the new WordPress Block Editor (Gutenberg). The licence is GPL-3.0.

When your agent uses it

  • The user asks to ensure quality
  • Run the quality gate
  • Validate before commit
  • After finishing substantive

Example prompts

  • “/ensure-quality”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Synthesize intent. Capture what the user set out to accomplish - goal, constraints, tradeoffs, ruled-in/out approaches - in their terms…
  2. Discover the project. Follow reference/discover.md. Record the chosen test commands, lint commands, standards sources, anti-slop /…
  3. Pin the fixed point. Default: merge-base of the current HEAD (and dirty worktree) against the first existing of: upstream tracking…
  4. Scope the diff. Include committed commits since the fixed point and uncommitted/staged work. Warn if on a default branch; still proceed.
  5. Skip flags. Run all four stages unless the user explicitly skips one (skip lint, lint only, …). Auto-invoke never skips.

What it can do on your machine

Read from SKILL.md and the folder at commit 5c13d80. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ensure Quality loads about 1.5k tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 707 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~115
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gambitph/Stackable at commit 5c13d80, republished under its GPL-3.0 licence (© gambitph). 707 words, ~1,495 tokens.

Download SKILL.mdSave it as .claude/skills/ensure-quality/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
ensure-quality
description
Local quality gate for the current worktree: review for risk/correctness (break, leak, undo intent), standards, spec, and anti-slop; then test, document, lint. Mechanical one-liner auto-fix and HITL for ask-user findings; ship-readiness summary. Use when the user asks to ensure quality, run the quality gate, validate before commit, or gate changes; after finishing substantive or AI-generated code changes; and always before the agent commits.

Ensure quality

Inner-loop quality gate: risk/correctness review plus anti-AI-slop. Asks whether the change will break, leak, or silently undo what the user wanted, and catches parallel structure, hand-synced catalogues, phantom names, and other common agent failure modes early. Moves review, test, docs, and lint closer to the work before it leaves the machine. No daemon, no second worktree, no push/PR - this skill is the gate.

Self-contained: everything needed lives under this skill folder. Project-agnostic: discover how this repo tests, lints, documents, and states maintainability rules - do not assume a stack.

Stages (order): review → test → document → lint. Load each stage file only when that stage runs. Load reference/discover.md once during preconditions. Anti-slop baseline: reference/anti-slop.md (always on during review; repo rules override on conflict).

When to run

Fire this skill when any of these hold:

  • The user asks to ensure quality / validate / gate / check before commit.
  • You just finished substantive source changes (feature, fix, refactor).
  • You are about to create a git commit.

Skip auto-invoke for pure Q&A, exploration with no edits, or when the user said to keep iterating without gating.

Preconditions

  1. Synthesize intent. Capture what the user set out to accomplish - goal, constraints, tradeoffs, ruled-in/out approaches - in their terms, enriched with decisions you made while working. A thin "fixed stuff" line is not enough; rewrite from conversation context first. This intent is authoritative acceptance criteria for the review stage.
  2. Discover the project. Follow reference/discover.md. Record the chosen test commands, lint commands, standards sources, anti-slop / maintainability docs, checklists, and doc surfaces for this run.
  3. Pin the fixed point. Default: merge-base of the current HEAD (and dirty worktree) against the first existing of: upstream tracking remote's default branch, then origin/develop, origin/main, origin/master, then local develop / main / master. Honor an explicit user override (since abc123, origin/main, …). Confirm the ref resolves.
  4. Scope the diff. Include committed commits since the fixed point and uncommitted/staged work. Warn if on a default branch; still proceed.
  5. Skip flags. Run all four stages unless the user explicitly skips one (skip lint, lint only, …). Auto-invoke never skips.

Completion: intent written, discovery recorded, fixed point named, diff non-empty (or report ready with nothing to gate and stop).

Show full SKILL.md (346 more words)Show less

Pipeline loop

For each stage in order:

  1. Read stages/<stage>.md and run it.
  2. Collect findings using the taxonomy in reference/findings.md.
  3. Auto-fix every auto-fix finding without asking, then re-run the stage. Cap at 2 auto-fix rounds for that stage; leftover findings escalate to HITL.
    • Review stage: auto-fix is mechanical one-liners only. After any review fix, follow the root-cause fixer rules and adversarial re-review in stages/review.md (treat fixer output as untrusted new code).
    • Test / document / lint: mechanical/low-risk auto-fix as each stage file allows.
  4. If any ask-user findings remain, pause - see HITL pause. Do not start the next stage until the pause resolves.
  5. no-op findings are reported only; nothing to do.
  6. If the stage stays red after rounds / declined fixes, go to Blocked.

Leave all quality fixes uncommitted unless the user already asked you to commit or ship.

HITL pause

Batch every current-stage ask-user finding in one message. Present each like a grill round - question, options, recommendation - then wait. When review recorded risk_level: high, prefer recommending careful fix over casual approve/skip.

⏸ **Quality gate - <stage>** (<n> ask-user findings)

❓ **F1** - **<short title>**: <verbatim finding: file, description, why it challenges intent or product behavior>

Options:
- **fix** - apply a fix (optionally with your guidance)
- **approve** - accept as-is and continue
- **skip** - drop this finding for this run
- **abort** - stop the whole gate

➡️ <your recommended option and one-line why>

Translate the user's answers into actions, apply agreed fixes, re-run the stage, then continue. For review-stage fixes agreed in HITL, still apply fixer discipline and adversarial re-review from stages/review.md. Do not paraphrase away finding detail. Do not continue past unresolved ask-user findings.

Blocked

Stop the pipeline. Leave fixes dirty. Emit the Summary with Ship readiness: blocked and the remaining findings. Do not commit. Do not claim green. Do not silently skip the failing stage.

Summary

Always end a completed or blocked run with this fixed brief (this order):

  1. Intent - short paragraph
  2. Risk - Low / Med / High + one sentence why (use the review-stage risk assessment when review ran)
  3. Diff scope - fixed point → worktree; key files
  4. Findings - counts by stage; call out risk-lens and anti-slop hits; auto-fixed vs HITL vs accepted vs remaining
  5. Tests run - commands + pass/fail; note skipped suites and why
  6. Docs - updated / checked / none needed
  7. Lint - commands + result
  8. Ship readiness - ready or blocked + what's left
  9. Uncommitted fix set - bullets if any quality fixes were applied

© gambitph, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files in .cursor/skills/ensure-quality of gambitph/Stackable.

  • SKILL.md
  • agents/openai.yaml
  • reference/anti-slop.md
  • reference/discover.md
  • reference/findings.md
  • reference/smells.md
  • stages/document.md
  • stages/lint.md
  • stages/review.md
  • stages/test.md

Open the folder on GitHubat commit 5c13d80

Compare with similar skills

Ensure Quality next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ensure Quality compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ensure Quality this skillgambitph/Stackable350—~1.5kAutomated safety check: PassGPL-3.0
Git PR Workflowandymai/brepjs114—~2.9kAutomated safety check: PassApache-2.0
Spec ReviewAI-Unified-Process/marketplace141—~2.9kAutomated safety check: PassApache-2.0
Code Completionfacioquo/stock-indicators-dotnet1.2k—~1.2kAutomated safety check: PassApache-2.0
Governing Quality Waiversjaktestowac/awesome-copilot-for-testers116—~2.4kAutomated safety check: PassMIT
Validatecortex-tms/cortex-tms180—~178Automated safety check: NotesMIT

Similar skills

  • Git PR Workflow

    andymai/brepjs

    This skill should be used when committing, pushing, branching, or merging in the brepjs repository — when a task involves "pre-commit hook failed" (which tier ran, how to bypass), "commit rejected…

    114 GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Spec Review

    AI-Unified-Process/marketplace

    Reviews the specification artifacts in docs/ (requirements, use case diagram, use case specifications, test cases, BPMN process models, entity model, glossary) against each other in two parts: a…

    141 GitHub stars~2.9k tokensUpdated 3 days ago
    Testing & QAAuto-check passed
  • Code Completion

    facioquo/stock-indicators-dotnet

    Quality gates for finishing work in this repository — dead-code cleanup, Roslynator and dotnet format fixes, markdownlint, build, unit tests, documentation, and Obsolete migration shims — with the…

    1.2k GitHub stars~1.2k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Governing Quality Waivers

    jaktestowac/awesome-copilot-for-testers

    Turns "we will skip this check for now" into a dated, attributed, expiring waiver with a stated reason and owner, inventories the silent skips already hiding in a repo - skipped tests, disabled lint…

    116 GitHub stars~2.4k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Validate

    cortex-tms/cortex-tms

    Run the full quality gate — tests, lint, build, and cortex-tms validate --strict.

    180 GitHub stars~178 tokensUpdated 3 days ago
    Testing & QAAuto-check: notes
  • Omh Verification Gate

    rlaope/oh-my-hermes

    [omh] Proof a change is done before merge: define and record build, lint, typecheck, test, security, docs, generated-output, and CI evidence before completion or merge.

    3.2k GitHub stars~2.3k tokensUpdated today
    Testing & QAAuto-check passed

More from gambitph/Stackable

All 18 skills in this repo
  • Wp Block Development

    gambitph/Stackable

    A skill your agent uses when developing WordPress (Gutenberg) blocks: block.json metadata, registerblocktype(frommetadata), attributes/serialization, supports, dynamic rendering…

    350 GitHub starsUsed in 4 repos~1.6k tokens
    Auto-check passed
  • Wp Block Themes

    gambitph/Stackable

    A skill your agent uses when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style…

    350 GitHub starsUsed in 3 repos~985 tokens
    Auto-check passed
  • Wp Performance

    gambitph/Stackable

    A skill your agent uses when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers)…

    350 GitHub starsUsed in 3 repos~1.5k tokens
    Auto-check passed
  • Wp Plugin Development

    gambitph/Stackable

    A skill your agent uses when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security…

    350 GitHub starsUsed in 3 repos~999 tokens
    Auto-check passed
  • Wp Project Triage

    gambitph/Stackable

    A skill your agent uses when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a…

    350 GitHub starsUsed in 4 repos~371 tokens
    Auto-check passed
  • A skill your agent uses when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware patterns, validating plugin naming or…

    350 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

Questions about Ensure Quality

What does Ensure Quality do?

Local quality gate for the current worktree: review for risk/correctness (break, leak, undo intent), standards, spec, and anti-slop; then test, document, lint. Ensure Quality is an agent skill from gambitph/Stackable. Local quality gate for the current worktree: review for risk/correctness (break, leak, undo intent), standards, spec, and anti-slop; then test, document, lint.

When should I use Ensure Quality?

Ensure Quality fits situations like: the user asks to ensure quality; run the quality gate; validate before commit; after finishing substantive.

How do I install Ensure Quality in Claude Code?

Run `npx skills add gambitph/Stackable --skill ensure-quality -a claude-code`. Or copy the skill folder (.cursor/skills/ensure-quality in gambitph/Stackable) into .claude/skills/ensure-quality in your project. Claude Code loads it when a task matches its description.

How do I install Ensure Quality in Codex?

Run `npx skills add gambitph/Stackable --skill ensure-quality -a codex`. Or copy the skill folder (.cursor/skills/ensure-quality in gambitph/Stackable) into .agents/skills/ensure-quality in your project. Codex loads it when a task matches its description.

Can I use Ensure Quality in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gambitph/Stackable --skill ensure-quality -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ensure-quality, .gemini/skills/ensure-quality, .github/skills/ensure-quality and .opencode/skills/ensure-quality in your project.

What does Ensure Quality need to run?

SKILL.md names no scripts, command-line tools or credentials: Ensure Quality is instructions for the agent only.

Does Ensure Quality access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ensure Quality safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ensure Quality use?

Ensure Quality is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ensure Quality use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ensure Quality?

Skills that share tags, products or a category with Ensure Quality: Git PR Workflow (andymai/brepjs, 114 stars), Spec Review (AI-Unified-Process/marketplace, 141 stars), Code Completion (facioquo/stock-indicators-dotnet, 1.2k stars) and Governing Quality Waivers (jaktestowac/awesome-copilot-for-testers, 116 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ensure Quality?

gambitph (a GitHub organization) maintains it in gambitph/Stackable, which has 350 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

Source: gambitph/Stackable on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.