Coding standards, frameworks, refactoring, and code review (15.2K skills)
Create Hookify rules that warn Claude or block operations when commands or file edits match specified conditions. The skill explains rule files, text matching patterns, multiple conditions, and how to test and refine the rules.
Migrate code and API calls from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Update platform-specific model identifiers and address reported prompt behavior issues, such as excessive tool use or unnecessary code complexity.
Create or improve skills for Claude Code plugins by defining clear activation conditions, writing focused instructions, and organizing supporting files. The guidance covers reusable scripts, reference documents, examples, and testing whether a skill activates for the intended requests.
Connect external services to Claude Code plugins through MCP, a protocol that exposes service functions as tools. Get guidance on server configuration, connection methods, authentication, tool permissions, and testing connections and tool calls.
Build Claude Code hooks, automated checks triggered by events such as tool use or session start. The guidance covers prompt-based decisions, command scripts, configuration, testing, and debugging for validation and workflow automation.
Build MCP servers that let AI access actions and data using mcp-use. The guide covers project setup, reusable prompts, interactive React interfaces, authentication, error handling, and deployment, with reference files for each area.
Compare a Git diff with its stated purpose to flag potentially unrelated files, added dependencies, API renames, and configuration changes. Receive recommendations to keep, split, or justify changes, with a proposed grouping for follow-up work.
Develop ChatGPT apps with interactive React widgets using mcp-use and OpenAI Apps SDK. Guidance covers app scope, server tools, shared state, and display settings. This skill is deprecated and points users to mcp-app-builder.
Inspect Python and JavaScript dependency files for missing version constraints, duplicate entries, conflicting exact versions, and outdated Python compatibility packages. Get plain-language explanations and focused repair suggestions, with offline checks by default.
A deprecated guide to building MCP servers with mcp-use, covering callable actions, data resources, reusable prompts, and interactive widgets. It includes design references and code examples, and directs users to the replacement skill, mcp-app-builder.
Review abandoned personal projects through local Git history to identify likely stopping points and recurring patterns. Compare revival candidates, select one worth revisiting, and outline concrete steps from checking whether it still runs to publishing it.
Investigate why a file or function exists using local Git history. Trace its introduction, later edits, authorship, and files often changed alongside it, then summarize likely intent and change risks while distinguishing evidence from inference.
Review Spec Kit code changes against relevant design documents, tests for expected and unwanted behavior, evidence that bug fixes prevent recurrence, and repository terminology. Findings identify the document sections behind design mismatches.
Process GitHub issues submitted for Spec Kit community extensions. Validate release details and required files, add or update the catalog and documentation table, and prepare a pull request with a validation summary.
Set up and use gstack in Capy or Claude Code for planning, code review, debugging, and release work. It checks the local environment, handles installation or repairs when needed, and selects the workflow instructions for the task.
Create engineering retrospectives from Git history, covering delivered changes, work patterns, test code ratios, and frequently changed files. Review individual contributions and improvement opportunities, save metrics, and compare results with earlier periods.
Turn a vague request into a precise specification through five phases and file it as a GitHub issue. Optionally start a Claude Code agent in a separate working directory to begin implementation.
Refresh gbrain's searchable code data to match the repository and update agent search guidance in CLAUDE.md. Use it to reindex a project or investigate searches that no longer find the expected code.
Remove the directory editing boundary set by `/freeze` so work can continue across all directories without ending the session. The existing freeze hooks remain registered, and `/freeze` can be used again to restore a boundary.
Investigate software errors by tracing code, reviewing recent changes, and reproducing symptoms. Test a specific cause before making a minimal fix, then verify the result with regression tests and a structured debug report.
Review an implementation plan before coding, checking system structure, data flow, diagrams, edge cases, test coverage, and performance. Discuss issues interactively with concrete recommendations to settle technical decisions before implementation begins.
Match a development request to an available gstack skill for planning, review, testing, shipping, documentation, or other tasks. It distinguishes testing from browser interaction and routes the request to the appropriate workflow.
Use OpenAI Codex CLI to review code changes, challenge an implementation by looking for ways it could fail, or discuss technical questions. Three modes provide an independent opinion, with follow-up questions supported in ongoing consultations.
Limit file edits to a chosen directory and block Edit, Write, and NotebookEdit operations outside it. Keep debugging or module changes within scope, with the restriction remaining active until explicitly removed.