claude

quality-gates

Engineering standards for agent-written code: gates (no comments, cyclomatic complexity, CRAP), the size rule and principles, and Matt Pocock's workflow skills.

1 on GitHubby CapitalCantripv0.13.0MITupdated 6 days ago
/

Plugin quality-gates from marketplace quality-gates in CapitalCantrip/quality-gates. Commands read from the repo's manifest — 6 days ago.

What it installs

Skills (26)

  • cc-python

    Cyclomatic complexity check for Python via cc-check (radon); flags functions above CC 8 and proposes refactors. Use when asked to check Python complexity.

  • cc-rust

    Rust complexity gate via cargo clippy (cognitive complexity > 10, functions > 25 lines); `setup` scaffolds clippy.toml and deny attributes.

  • cc-swift

    Swift complexity check via SwiftLint and crap --lang swift (lizard); flags functions above the threshold and proposes refactors.

  • cc-typescript

    Cyclomatic complexity check for TypeScript and JavaScript via cc-check --lang typescript (lizard); flags functions above CC 8 and proposes refactors. Use when asked to check TypeScript or JavaScript complexity.

  • codebase-design

    Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

  • crap

    Quality gate for Python, Swift or TypeScript/JavaScript: CRAP scores (CRAP > 8 = FAIL). Use when asked about complexity, coverage, or whether code passes the gate.

  • diagnosing-bugs

    Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

  • domain-modeling

    Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

  • grill-with-docs

    A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

  • handoff

    Compact the current conversation into a handoff document for another agent to pick up.

  • implement-spec

    Implement the result of /to-spec and /to-tickets in code.

  • implement

    Implement a piece of work based on a spec or set of tickets.

  • improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

  • no-comments

    Set up or run the no-code-comments gate (comment-debt) in a repo, or pay down one file's comment debt. Use when adding the gate to a project, when comment-debt fails, or when asked to convert or pay down comments.

  • pr

    Use when writing a PR body.

  • retro

    Conduct a retrospective on a coding session.

  • review-against-spec

    Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them s

  • setup-matt-pocock-skills

    Matt Pocock's skills send you here when docs/agents/ is missing. In a project on quality-gates, /setup-standards does that setup.

  • setup-standards

    Set up or upgrade a project for the quality-gates standards: issue tracker and agent docs, gates, baselines, hooks, CI and the asking rule. Use when asked to set up the standards, or after bumping the quality-gates pin.

  • standards

    Engineering principles and the size rule for agent-written code. Use when choosing where to start a piece of work, before declaring work done, before putting a question to the builder, when a correction recurs, or when a principle is named (prove it works, subtract before you add, ...).

  • tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

  • to-spec

    Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

  • to-tickets

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

  • triage

    Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

  • wayfinder

    Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

  • writing-for-agents

    Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

View source on GitHub

Maintain quality-gates?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted