review
General code review for staged changes or specified files. Use when reviewing pull requests, commits, or code changes across any language.
Explore AI skills for development, content, data and productivity. Compare the description and repository popularity before opening a skill.
General code review for staged changes or specified files. Use when reviewing pull requests, commits, or code changes across any language.
Lint and format Go code via golangci-lint. Use when asked to lint code, fix lint errors, or check code quality.
Python refactoring triggers and guidelines for code size limits
Semantic code search - finds code by meaning, not just keywords. Helpful when: - User asks WHERE or HOW something is implemented ("where is X handled", "how does Y work", "where are Z". "how are X", "explain Y"...
Python naming conventions for variables, constants, files, and directories
Use when asked to create or update skills or extend agent capabilities in this configuration.
Summarize Discord chat messages across servers. Use when user asks for chat summary, digest, highlights, recap, or overview of Discord conversations.
Use when encountering bugs, test failures, unexpected behavior, or performance issues before proposing fixes.
Structured problem-solving methodology. Activates for planning, design, debugging, or complex multi-step tasks. Use for systematic analysis and evidence-based reasoning.
Systematic analysis and reasoning workflows. Use when performing audits, investigation, requirements analysis, risk analysis, scenario/edge-case enumeration, or design analysis that demands evidence-based, comp...
Break a problem into atomic, testable subproblems. Use when facing complex tasks, unclear requirements, or planning implementation strategy.
Use when receiving code review feedback before implementing suggestions, especially if unclear or questionable.
TODO list discipline for task tracking. Activates for multi-step tasks (3+), complex work, or when systematic organization is needed. Use for tracking progress and ensuring completeness.
Use when user provides a list of Linear issue IDs to fix sequentially; enforce status transitions (In Progress -> In Review), one issue at a time, and report build/test confirmation strategy.
MUST use for any non-trivial development task in advent-pdp11 - implements iterative development with status tracking, session logging, validation, and one-task-at-a-time approach. Use when implementing feature...
Use when about to claim work is complete, fixed, or passing, or before committing/creating PRs; requires fresh verification evidence before any success claim.
Develop, maintain, and audit Go analyzers (go/analysis). Use when creating/updating analyzers, suggested fixes, analysistest golden files, or integration analyzer harnesses.
Run full pre-commit workflow for Go code. Use when preparing to commit Go changes, before creating pull requests, or ensuring code quality.
View call logs for the Vocal Bridge voice agent. Can list recent calls or show details of a specific session including transcript.
Show call statistics for the Vocal Bridge voice agent including total calls, success rate, and average duration.
Stream real-time debug events from the Vocal Bridge voice agent. Shows transcriptions, agent responses, tool calls, and errors.
Show information about the connected Vocal Bridge voice agent including name, mode, phone number, and deployment status.
Manage the system prompt for the Vocal Bridge voice agent. Can show, edit, or set the prompt and greeting.
Use this skill when the user expresses ANY intent related to issue/thread management: - Switching issues: "let's work on X", "switch to #Y", "go to the auth issue" - Checking status: "what are we working on?",...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.