code-quality
477
receive-review
处理 reviewer 反馈：Red→Green 修复 + 技术论证（禁止表演性同意）。 Use when: 收到 review 结果、reviewer 提了 P1/P2、需要处理反馈。 Not for: 发 review 请求（用 request-review）、自检（用 quality-gate）。 Output: 逐项修复确认 + reviewer 放行。
zts212653
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
testing
477
quality-gate
开发完成后的自检门禁：愿景对照 + spec 合规 + 验证。 Use when: 开发完了准备提 review、声称完成了、准备交付。 Not for: 收到 review 反馈（用 receive-review）、merge（用 merge-gate）。 Output: Spec 合规报告（含愿景覆盖度）。
zts212653
testing-security
testing
477
request-review
向跨家族 peer-reviewer 发送 review 请求（含五件套）。 Use when: 自检通过后准备请其他猫 review。 Not for: 收到 review 结果（用 receive-review）、自检（用 quality-gate）。 Output: Review 请求信（存档到 review-notes/）。
zts212653
testing-security
code-quality
476
ralph-wiggum
强制 Stop hook loop，避免 Codex 只做一步就停止；直到满足“完成承诺”才允许结束并输出总结。
stellarlinkco
testing-security
code-quality
475
aif-best-practices
Code quality guidelines and best practices for writing clean, maintainable code. Covers naming, structure, error handling, testing, and code review standards. Use when writing code, reviewing, refactoring, or asking "how should I name this", "best practice for", "clean code".
lee-to
testing-security
code-quality
475
aif-fix
Fix a specific bug or problem in the codebase. Supports two modes - immediate fix or plan-first. Without arguments executes existing FIX_PLAN.md. Always suggests test coverage and adds logging. Use when user says "fix bug", "debug this", "something is broken", or pastes an error message.
lee-to
testing-security
code-quality
475
aif-grounded
Reliability gate for answers. Forces evidence-based reasoning, explicit uncertainty, and “insufficient information” instead of guesses. Use when user says “be 100% sure”, “no hallucinations”, “only if verified”, “grounded answer”, or when stakes are high.
lee-to
testing-security
code-quality
475
aif-improve
Refine and enhance an existing implementation plan with a second iteration. Re-analyzes the codebase, checks for gaps, missing tasks, wrong dependencies, and improves the plan quality. Use after /aif-plan to polish the plan before implementation, or to improve an existing /aif-fix plan.
lee-to
testing-security
code-quality
475
aif-review
Perform code review on staged changes or a pull request. Checks for bugs, security issues, performance problems, and best practices. Use when user says "review code", "check my code", "review PR", or "is this code okay".
lee-to
testing-security
code-quality
475
aif-verify
Verify completed implementation against the plan. Checks that all tasks were fully implemented, nothing was forgotten, code compiles, tests pass, and quality standards are met. Use after "/aif-implement" completes, or when user says "verify", "check work", "did we miss anything".
lee-to
testing-security
testing
473
tests-developer
Smart router to testing patterns and practices. Use when writing unit tests, creating mocks, testing edge cases, or working with Swift Testing and XCTest frameworks.
anyproto
testing-security
code-quality
473
self-review
Agent self-reviews its own diff against TASTE_INVARIANTS.md before presenting to user. Catches mechanical violations early.
anyproto
testing-security
code-quality
471
code-review
Review code changes for bugs, security issues, and improvements
victordibia
testing-security
testing
469
detect-flaky-tests
Identify flaky tests by comparing failures across multiple CI runs. Use when the user suspects flaky tests, sees intermittent failures, or wants to analyze test reliability.
Sovereign-Labs
testing-security
code-quality
468
check-code-quality
Run comprehensive Rust code quality checks including compilation, linting, documentation, and tests. Use after completing code changes and before creating commits.
r3bl-org
testing-security
code-quality
468
write-documentation
Write and format Rust documentation correctly. Apply proactively when writing code with rustdoc comments (//! or ///). Covers voice & tone, prose style (opening lines, explicit subjects, verb tense), structure (inverted pyramid), intra-doc links (crate:: paths, reference-style), constant conventions (binary/byte literal/decimal), and formatting (cargo rustdoc-fmt). Also use retroactively via /fix-intradoc-links, /fix-comments, or /fix-md-tables commands.
r3bl-org
testing-security
code-quality
468
run-clippy
Run clippy linting, enforce comment punctuation rules, format code with cargo fmt, and verify module organization patterns. Use after code changes and before creating commits.
r3bl-org
testing-security
code-quality
466
yaml-validator
Validate Hyper-Extract YAML templates for syntax and structure errors. Use when user says: "validate template", "check YAML", "fix errors", "validate syntax". Trigger: User wants to verify their YAML configuration is correct. Skip: User wants to design a new template (use record-designer or graph-designer instead).
yifanfeng97
testing-security
code-quality
465
agent-session-format-check
Verify agent session format compatibility for Agent Sessions. Use when any agent CLI updates, when monitoring flags drift, or when bumping max verified versions (fixtures + docs + tests). Covers session schema, usage/limits tracking, storage backends, and discovery path contracts for all supported agents.
jazzyalex
testing-security
code-quality
465
qmlpreviewer
Auto-detects the active QML file from editor context, runs qmlscene, and copies the rendered image to the clipboard by default. Invoke when user asks to preview or visually verify QML UI.
mengps
testing-security