claude

quality-workflow

Sister to feature-workflow for code-quality findings. Surfaces, triages, and resolves static-analysis output (skylos for Python, fallow for TS/JS) with the same backlog-and-epic discipline. User-invocable skills: /quality-verify-hook self-tests pre-commit hooks against known-bad fixtures (catches the silently-misconfigured-hook class of bug), /quality-audit produces fingerprinted snapshots + NEW/RESOLVED/PERSISTING delta (suppressed findings excluded from active counts), /quality-unblock triages failing hooks with playbook-driven fix/suppress/defer proposals and refuses bare suppressions. Plus the language-agnostic suppression-discipline standard (every ignore carries an inline rationale). Day-1 playbooks for 13 skylos + 12 fallow rule_ids.

14 on GitHubby Court Schuettv0.3.0updated 1 month ago
/

Plugin quality-workflow from marketplace schuettc-claude-code-plugins in schuettc/claude-code-plugins. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (4)

  • quality-audit

    Read-only static-analysis snapshot. Runs skylos (Python) and fallow (TS/JS) full audits, writes a fingerprinted snapshot to .claude/quality-snapshots/YYYY-MM-DD.json, and renders a grade card plus delta vs the previous snapshot (NEW / RESOLVED / PERSISTING findings). Use when the user asks "what's m

  • quality-unblock

    Triage a failing pre-commit hook (skylos or fallow). For each finding, look up the rule in the day-1 playbook and present three options — fix in code, suppress with a required # Why: justification, or defer to feature-workflow as a tech-debt epic. Use when a commit fails because of a quality hook, w

  • quality-verify-hook

    Verify that a project's static-analysis git hooks actually fire on bad code — works with lefthook or the pre-commit framework. Use after installing the quality stack (lefthook install), after editing lefthook.yml / .pre-commit-config.yaml, or whenever the user asks "is the hook working?" / "test the

  • suppression-discipline

    The rule for suppressing static-analysis findings in any language — every suppression carries an inline rationale, and bare suppressions are a quality failure to fix. Use when someone adds or proposes a lint/analysis ignore (# skylos: ignore, # noqa, # type: ignore, # fallow-ignore, // eslint-disabl

View source on GitHub

More from schuettc/claude-code-plugins

All 7 plugins →

Feature lifecycle management with state, search, epic dispatch, and review gates. Capture ideas, plan, and ship as files (idea.md → plan.md → shipped.md) with orthogonal state (active/paused/replaced/abandoned). Single-feature autopilot and parallel-wave epic dispatch — every subagent in its own worktree, with a local CI-parity preflight gate before every push. Per-feature review override (external Gemini/Codex CI / internal subagent / skip). Auto-generated DASHBOARD.md with Paused, Epics, and Validation Warnings sections. Multi-repo workspaces: an aggregated cross-repo dashboard, cross-repo epics, contract-edit warnings, and coordinated producer-first deploy.

18 skills · 12 agents · hooks

14

Guided workflow to deploy Node.js/Express apps to AWS serverless architecture. Analyzes your app, scaffolds infrastructure, and deploys with CDK — all with step-by-step explanations for beginners.

9 skills · 1 agent · 2 MCP servers

14

ghost

claude

Write, revise, and push blog posts to a Ghost site from Claude Code — a Ghost Admin API MCP plus a plan→draft→revise→push skill set.

7 skills · 1 MCP server

14

Evergreen engineering standards I hold code to — the judgment layer that AI-slop resistance needs on top of the mechanical quality stack. Project-structure conventions (consistent layout + naming so every repo looks the same), worktree isolation (every line of work in its own tree so parallel work never collides), and GitHub API discipline (zipball over per-file, rate-limit backoff), with automation-auth (GitHub App vs PAT) and hook-escape conventions on the way. Pure advisory skills that fire when the situation matches — no tooling, no setup, safe to leave enabled for a project's whole life. Backed by lessons from real incidents.

6 skills

14

Sprint planning and team coordination. Triage backlogs by deadline, assign work with self-service specs, audit feature specs for completeness, and generate team communication. Designed for small teams with mixed experience levels.

5 skills

14

One-shot setup for a new repo's standards: feat → dev → main promotion model with a PR CI gate, GitHub repo setup (branch protection, deploy environments, required reviewers, environment-scoped OIDC), and the language-agnostic quality stack (lefthook hooks + a shared justfile, run identically in CI). The /project-init skill detects current state and applies only the missing patterns — on new repos and existing ones alike, plus an on-ramp for multi-repo workspaces (scaffold a coordination repo via feature-init --workspace). Setup-only and disposable: the evergreen standards live in the engineering-standards and quality-workflow plugins, pulled in as dependencies. Backed by lessons from real incidents.

4 skills

14

Maintain quality-workflow?

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 plugins7 plugins