Browse Skills

Pull Request Review runs a structured multi-agent workflow to review GitHub pull requests, using parallel specialized reviewers, adversarial verification, and false-positive filtering to produce actionable feedback. Use it when someone asks to review a PR, check a pull request, or references a PR number or GitHub PR URL.

Swift Concurrency diagnoses Swift concurrency issues, refactors callback-based code to async/await, and guides Swift 6 migration when working with tasks, actors, @MainActor, Sendable, data races, thread safety, or concurrency-related compiler and linter warnings.

Dev Design runs the design review phase for configured AI docs features. Use it to validate architecture, review design docs, resolve trade-offs, or run dev-lifecycle phase 3.

Dev Implementation provides implementation-phase guidance for executing feature plans and checking implementation against design. Use it when implementing planned tasks, updating implementation docs, verifying code matches design, or running dev-lifecycle phases 5 and 7.

Dev PR publishes a ready feature branch for code review on GitHub, GitLab, or another Git host. Use it after the commit workflow to sync, push, and open or update a review request.

Dev Review runs final pre-push code review for AI-assisted development. Use it when you need holistic code review, design alignment checks, integration risk review, or dev-lifecycle phase 9 verification.

Dev Testing guides adding and validating feature test coverage for AI docs features, including unit and integration tests, running coverage, and closing gaps. Use it when the user wants to write tests, update testing docs, run coverage, or run dev-lifecycle phase 8.

Security Review finds vulnerabilities in code, skills, and prompts — including OWASP Top 10, prompt injection, business logic flaws, and insecure defaults — before they ship. Use it when reviewing PRs, auditing modules, reviewing AI skills/prompts, or preparing for release.

Simplify Implementation analyzes existing code to reduce complexity, improve maintainability, and enhance scalability. Use it when asked to simplify code, refactor for readability, clean up implementations, reduce technical debt, or make code easier to understand.

Structured Debugging guides evidence-first debugging before code changes by clarifying expected behavior, reproducing issues, identifying likely root causes, and agreeing on a fix plan with validation steps. Use when debugging bugs, regressions, incidents, failing tests, or running root cause analysis.

TDD enforces a red-green-refactor cycle: write a failing test before any production code. Use it when implementing new functionality, adding behavior, or fixing bugs.

Verify enforces evidence-based completion claims by requiring fresh terminal output before an agent reports success. Use it when completing any task, fixing a bug, finishing a phase, or running tests, builds, or deployments.