quality plugins

by OpenAI Codex

Evaluate Codex skills and plugins from chat with a beginner-friendly start command, local-first reports, token budget explanations, and guided benchmarking.

by severity1

Severity level classification and prompt improvement for marketplace plugins. Assigns severity ratings (S1-Critical through S4-Low) and enhances plugin prompts for clarity, safety, and effectiveness.

by Avi Fenesh

Multi-agent iterative code review until zero issues remain

by Lev Nikolaevich

Risk-based test portfolio planning and reproducible acceptance-test lifecycle.

by xiaolai

Natural-Language Programming reference knowledge — the 50 Rules, the 100-point scoring rubric, per-tool conventions (Claude Code / Codex CLI / Antigravity), anti-patterns, vocabulary discipline, and authoring guides, as loadable Codex skills. The interactive linting commands remain a Claude Code plugin; the cross-tool deterministic checker ships as a standalone Python binary (bin/nlpm-check).

by Alberto Leal

Review and ensure skills maintain high quality standards. Use when creating new skills, updating existing skills, or auditing skill quality. Checks for progressive disclosure, mental model shift, appropriate scope, and documentation clarity.

by Coalesce Labs

Complete development workflow: research → plan → implement → validate → ship. Includes research agents, planning tools, handoff system, Linear integration, and PM commands.

by Surah Li

Iteratively improve any skill using eval-grounded autoresearch and Hamel's Three Gulfs methodology.

by Patrick D'appollonio

Hostile, bias-free review using independent reviewers, false-positive verification, and validated fixes.

by Stellars Henson

Autonomous build iteration orchestrator. Runs structured improvement cycles with multi-agent review, FSM-driven phase lifecycle, per-phase gates, and YAML-configured workflows.

by John Wilger

John's consolidated development workflow, engineering standards, worktree, task, review, and agentic-system tooling.

by ncaq

Code review for PRs or local changes. Covers code quality, dependency updates, performance, test coverage, documentation accuracy, and security.

by Mingyang Bao

Post-feature sharp review — 3 parallel reviewers with schema enforcement, merge findings, sync task list

by Ivan-WG

Candour as a mechanism, not a pep talk. One blocking Stop gate, five clauses a script can prove: a file:line citation resolving to no file or past its end; a position retracted after bare pushback with no tool call in between; a completion claim after edits with nothing executed since; a task-runner run stopping without its recorded gate pass; a dependency map changed with an untouched lockfile. Flattery, apologies and defensive phrasing are counted by /candor:check and blocked by nothing, on purpose. Plus the terse reply mode (/candor:level lite|full|ultra|off): chat-message brevity as a shape contract — prose-line budgets and a fixed report skeleton, never less work in the turn.

by Ivan-WG

Engineering process: plan-before-code, YAGNI, SOLID principles applied with judgment, task orchestration, work verification — held at Stop by candor's gate (clause 3, refusing a completion claim when files were edited but nothing ran afterward) when candor is installed; without it the rule is prose — low-cognitive-load code, KISS/DRY simplicity principles. Owns structure at both levels: code (units, interfaces, file placement) and system (service boundaries on data ownership, scaling paths, cache placement, sync vs async integration, domain modeling) via the system-design and domain-modeling skills and the system-architect worker.

by Ivan-WG

Stack-agnostic code review: correctness bugs, code smells, convention drift on any diff or PR — severity-sorted one-line findings — plus comment discipline: every fact routed to the artifact that cannot lie about it, comments spent only on why-not-the-obvious, external constraints, intentional silence and contract facts (default: no comment; write-time hooks warn, and deny the three strictest patterns plus any whole file over a 0.4:1 comment ceiling, once per file per session; /code-review:comment-review). Defers structure/YAGNI to code-architecture, security depth to security, stack idioms to the per-framework review plugins. Includes /code-review:review, a code-reviewer agent, the code-smells, reuse-hygiene and comment-discipline skills. The fan-in for overlapping review surfaces: loads every installed matching stack skill in one pass.

by Nery Samuel Murillo

Audit and propose repository-first Prettier configuration with explicit approval before any repository mutation.

by Ivan-WG

Systematic debugging: root cause before any fix — reproduce first, read the actual error, isolate with hypothesis tests and bisection, one change at a time, verify against the original symptom; escalation rule after three failed fixes. Ships a delegatable debugger agent for handing off the long reproduce-bisect investigation. Includes /debugging:debug.

by dunnock

Create comprehensive Fishbone (Ishikawa/Cause-and-Effect) diagrams for structured root cause brainstorming. Guides teams through problem definition, category selection (6Ms, 8Ps, 4Ss, or custom), cause identification, sub-cause drilling, prioritization via multi-voting, and 5 Whys integration. Generates visual SVG diagrams and professional HTML reports. Use when brainstorming potential causes, conducting root cause analysis, facilitating quality improvement sessions, analyzing defects or failures, structuring team problem-solving, or when user mentions "fishbone", "Ishikawa", "cause and effect diagram", "6Ms", "cause analysis", or "brainstorming causes".

by dunnock

Conduct rigorous 5 Whys root cause analysis with guided questioning, quality scoring, and professional report generation. Use when performing root cause analysis, investigating problems, conducting 5 Whys sessions, troubleshooting recurring issues, or when user mentions "5 whys", "root cause", "why did this happen", "find the cause", or needs to identify underlying causes of defects, failures, or process problems. Includes validation tests, scoring rubric, and countermeasure development.

by Ivan-WG

Independent stronger-model second opinion at key moments — stuck debugging or an imminent irreversible action. /fresh-take:consult composes a facts-only brief (no leaning) and dispatches a blind stronger-model consultant with read-only repo access; it returns a Take, Risks, and one Alternative. A UserPromptSubmit reminder hook nudges the command on key-moment phrases. Advice only — it never blocks, gates, or edits anything.

by Ivan-WG

Prices every output as a debit and asks how much. Five surfaces, one bar each: code, tests, comments, files, and actions — a tool call, subagent spawn or verify pass whose result cannot change the next step is a paid no-op, and nothing else here prices that. Only four things buy more than the minimum: blast radius, an observed defect, a stated criterion, the user asking; the excess must name which, where it happens. Minimum means risk coverage, not count — never delete a test to hit a ratio.

by dunnock

Conduct Pareto Analysis (80/20 Rule) to identify the vital few causes driving the majority of problems. Guides data collection, category definition, chart creation, cumulative percentage calculation, and prioritization. Generates professional Pareto charts (SVG) and HTML reports with quality scoring. Use when prioritizing defects, complaints, failures, or improvement opportunities; when user mentions "Pareto", "80/20 rule", "vital few", "trivial many", "prioritization", or needs to identify which factors contribute most to a problem.

by Kyle Tabor

Pre-mortem analysis skill — define success/failure criteria before execution. Forces agents to articulate what bad output looks like before starting multi-step work. Based on Gary Klein's prospective hindsight research.