Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
feature-spec-moderator
Chief Architect review - critically evaluate peer feedback on an engineering spec. Integrate valid suggestions, push back on scope creep, and maintain alignment with the PRD. Enforce startup simplicity.
pcortes/swarm-attack 1
-
bug-fix-plan-moderator
pcortes/swarm-attack 1
-
qa-contract-validator
Validates API contracts by discovering consumers and ensuring responses match their expectations. Detects breaking changes.
pcortes/swarm-attack 1
-
bug-fix-plan-critic
pcortes/swarm-attack 1
-
fix-planner
Design fix plans based on root cause analysis. Use after root cause is identified to plan specific code changes and test cases needed to fix the bug.
pcortes/swarm-attack 1
-
issue-creator
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
pcortes/swarm-attack 1
-
qa-behavioral-tester
Executes behavioral API tests by spinning up the service and making real HTTP requests. Validates status codes, response structure, and data correctness.
pcortes/swarm-attack 1
-
feature-spec-author
Draft detailed engineering specs from an approved PRD. Use when generating or updating the engineering specification for a feature, before implementation begins.
pcortes/swarm-attack 1
-
feature-verifier
Analyze test failures and suggest fixes for Feature Swarm verification. Use when tests fail during the verification phase to diagnose root cause and determine if automatic recovery is possible.
pcortes/swarm-attack 1
-
summarizer
pcortes/swarm-attack 1
-
qa-regression-scanner
Analyzes code diffs to identify affected endpoints and prioritize regression testing. Focuses QA effort on changed areas.
pcortes/swarm-attack 1
-
feature-spec-critic
Review and score engineering specs against a startup-focused quality rubric. Penalize over-engineering and reward simplicity.
pcortes/swarm-attack 1
-
bug-root-cause-critic
pcortes/swarm-attack 1
-
backlog-champion
Champion prioritization of discovered opportunities. Advocates for the most impactful, actionable items based on team velocity, business value, and technical feasibility.
pcortes/swarm-attack 1
-
coder
Implementation Agent: Full TDD workflow in a single context window. Writes tests, implements code, and iterates until all tests pass.
pcortes/swarm-attack 1
-
backlog-moderator
Business moderator for backlog prioritization debates. Synthesizes Champion and Critic views into final rankings. Optimizes for team productivity and sustainable velocity.
pcortes/swarm-attack 1
-
qa-orchestrator
Coordinates adaptive QA testing across behavioral, contract, and regression dimensions. Routes to specialized sub-agents based on context and depth.
pcortes/swarm-attack 1
-
root-cause-analyzer
Analyze reproduction evidence to identify the root cause of bugs. Use after reproduction to trace execution and find the exact location and reason for the failure.
pcortes/swarm-attack 1
-
qa-semantic-tester
Semantic QA testing using Claude Code CLI with Opus 4.5
pcortes/swarm-attack 1
-
issue-validator
Validate generated GitHub issues for completeness and implementability. Reviews each issue for clear scope, actionable acceptance criteria, and sufficient context for implementation.
pcortes/swarm-attack 1
-
bug-researcher
Reproduce bugs and gather evidence for root cause analysis. Use when investigating a bug report to confirm reproduction and collect detailed information about the failure.
pcortes/swarm-attack 1
-
feature-recovery
Analyze implementation failures and generate recovery plans. Use when an issue fails and needs diagnosis for retry or escalation.
pcortes/swarm-attack 1
-
feature-spec-moderator
Apply critic feedback to improve an engineering spec. Use when revising a spec based on review comments to address issues and improve quality scores.
pcortes/swarm-attack 1
-
fix-planner
Design fix plans based on root cause analysis. Use after root cause is identified to plan specific code changes and test cases needed to fix the bug.
pcortes/swarm-attack 1