pmco23
@pmco23
Public Skills
backend-audit
by pmco23
Use after build is complete to audit backend code against the project style guide. Supports Go, Python, TypeScript, and C# backends. Checks naming, error handling patterns, package structure, and API conventions. Requires .pipeline/build.complete.
doc-audit
by pmco23
Use after build is complete to audit CHANGELOG.md for format compliance, completeness, and feature coverage. Requires .pipeline/build.complete.
frontend-audit
by pmco23
Use after build is complete to audit frontend code against the project style guide. Checks TypeScript/JavaScript/CSS/HTML conventions, naming, component patterns, and accessibility basics. Requires .pipeline/build.complete.
cleanup
by pmco23
Use after build is complete to strip dead code, unused imports, unreachable branches, and commented-out code. Requires .pipeline/build.complete. Safe to run standalone or as part of /qa pipeline.
qa
by pmco23
Use after /build to run the full post-build QA pipeline. Supports --parallel (all audits simultaneously) or --sequential (denoise → qf → qb → qd → security-review in order). Requires .pipeline/build.complete.
security-review
by pmco23
Use after build is complete to scan for OWASP Top 10 vulnerabilities. Checks injection, authentication, authorization, data exposure, and misconfiguration risks. Requires .pipeline/build.complete.
pack
by pmco23
Pack the local codebase using Repomix CLI into three targeted snapshots (code, docs, full) stored in .pipeline/ for sharing across /qa audit agents. Run before /qa for maximum token efficiency. Usage: /pack [path] (defaults to cwd).
git-workflow
by pmco23
Use before any destructive git operation (force-push, reset --hard, branch -D, rebase on published commits). Verifies the target, explains the consequences, and requires explicit confirmation. Not needed for routine commits, branch creation, or PRs — those are governed by CLAUDE.md git conventions.
build
by pmco23
Use after /plan to execute the build. Opus leads and coordinates; Sonnets implement. Supports --parallel (independent agent per task group, own context) or --sequential (one task group at a time in current session). Invokes drift-verifier agent post-build. Writes .pipeline/build.complete on pass.
quick
by pmco23
Use when implementing small features, bug fixes, typo corrections, config tweaks, or any well-understood change that does not require the full pipeline. Completely independent of the brief/design/review/plan/build/qa flow. Use --deep to escalate to Opus for trickier problems.
brief
by pmco23
Use when starting a new feature, project, or task - extracts requirements, constraints, non-goals, style preferences, and key concepts from fuzzy input through conversational Q&A. Output is a structured brief saved to .pipeline/brief.md. Always run this before /design.
init
by pmco23
Use when starting a new project or adding missing boilerplate to an existing one. Generates CLAUDE.md, README.md, CHANGELOG.md, CONTRIBUTING.md, and .github/pull_request_template.md adapted to the project's language, stack, and context. Asks before overwriting any existing file.
reset
by pmco23
Use to reset the pipeline to a specific phase. Removes downstream artifacts while preserving upstream ones. Detects current phase, offers reset targets, confirms before deleting. No gate — always available when a pipeline is active.
review
by pmco23
Use after /design to adversarially review the design document. Dispatches strategic-critic (Opus) and code-critic (Sonnet) in parallel — Opus for strategic critique grounded in Context7, Sonnet for code-grounded critique against the existing codebase. Lead deduplicates, runs cost/benefit analysis, loops until all MUST FIX findings resolve. Writes .pipeline/design.approved on loop exit.
status
by pmco23
Use at any time to check pipeline state and get next-step guidance. When no pipeline is active, shows available workflow options and paths. No gate — always available.
design
by pmco23
Use after /brief to transform a brief into a formal design document. Performs first-principles analysis, classifies constraints, grounds all recommendations in live library docs via Context7 and web search, then iterates until alignment. Writes .pipeline/design.md.
plan
by pmco23
Use after /review to transform the approved design into an atomic execution plan. Writes task groups with exact file paths, complete code examples, and named test cases with assertions. Build agents must never need to ask clarifying questions. Writes .pipeline/plan.md.
tdd
by pmco23
Apply when asked to enforce TDD, practice test-driven development, write test first, or follow Red-Green-Refactor. Enforces the Iron Law — no production code without a failing test first. Covers the full Red-Green-Refactor cycle, when TDD applies, and valid exceptions.
drift-check
by pmco23
Use to detect drift between a source-of-truth document and a target document or implementation. Dispatches drift-verifier (Sonnet) and path-verifier (Sonnet) in parallel — semantic claim analysis and structural path/symbol verification. Requires .pipeline/plan.md. Used internally by /build and available standalone.
test
by pmco23
Use to run the project test suite. Supports /test [file-or-pattern] to scope to specific files or test names. Detects jest, vitest, go test, pytest, dotnet test, and cargo test automatically. No pipeline artifacts required — can run at any time.
rollback
by pmco23
Use to undo a completed build. Reads .pipeline/plan.md to identify which files were created or modified by each task group, presents a checklist for confirmation, removes or restores confirmed files, and resets .pipeline/build.complete. Requires .pipeline/build.complete.