build
01Agent
π¨ Implement the next task incrementally β TDD cycle with build, test, verify, commit. Picks the next pending task, writes failing tests, implements code, and verifies everything passes before committing.
Agent
π¨ Implement the next task incrementally β TDD cycle with build, test, verify, commit. Picks the next pending task, writes failing tests, implements code, and verifies everything passes before committing.
Agent
π Senior code reviewer that evaluates changes across five dimensions β correctness, readability, architecture, security, and performance. Saves review to docs/reviews/ and creates GitHub issues for each finding.
Agent
β¨ Simplify code for clarity and maintainability β reduce complexity without changing behavior. Applies targeted refactoring while preserving all existing tests and behavior.
Agent
π― Reusable orchestrator agent that triages open GitHub issues, categorizes them by type (security, bug, code-quality, testing, documentation, dependency), and dispatches the appropriate sub-agent to resolve each one. Works in any repository β discovers project context from repo metadata and conventions files atβ¦
Agent
π Break work into small verifiable tasks with acceptance criteria and dependency ordering. Read-only planning β no code changes.
Agent
ποΈ Conduct a five-axis code review β correctness, readability, architecture, security, and performance. Tailored to the WHOOP MCP project with project-specific checks.
Agent
π‘οΈ Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Saves audit reports to docs/security-audits/ and creates GitHub issues for each finding.
Agent
π Run the pre-launch checklist and prepare for npm publish + Claude Desktop integration. Covers code quality, security, packaging, integration testing, and documentation.
Agent
π Start spec-driven development β write or update the WHOOP MCP server specification before writing code. Defines what to build, why, and how to verify it's done.
Agent
𧬠QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
Agent
π§ͺ Run TDD workflow β write failing tests, implement, verify. For bugs, use the Prove-It pattern (write a test that reproduces the bug before fixing it).
Instructions file GitHub Copilot
Instructions for shashankswe2020-ux/whoop-mcp, covering project: whoop-mcp, tech stack, commands, code conventions and testing.
Skill Claude CodeCodex
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Skill Claude CodeCodex
Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.
Skill Claude CodeCodex
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Skill Claude CodeCodex
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Skill Claude CodeCodex
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Skill Claude CodeCodex
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
Skill Claude CodeCodex
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
Skill Claude CodeCodex
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
Skill Claude CodeCodex
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Skill Claude CodeCodex
Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
Skill Claude CodeCodex
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.
Skill Claude CodeCodex
Refines ideas iteratively. Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.