Coding standards, frameworks, refactoring, and code review (16.3K skills)
Investigate bugs by tracing symptoms through code and recent changes, reproducing failures, and testing a specific cause before fixing it. Produce a focused correction, a regression test to catch recurrence, and an evidence-based debugging report.
Analyze files or modules for duplicated code, excessive complexity, and violations of SOLID, five software design principles. Get prioritized refactoring suggestions with affected locations, risks, estimated effort, and testing needs to guide code improvements.
Compare alternative ways to solve a coding problem, including when each approach fits and its advantages and drawbacks. Get a comparison table and a recommendation based on the current context, with code examples in detailed mode.
Audit Claude Code instruction rules against actual project files to find broken settings, overly broad scopes, and loading issues. Review each rule’s usefulness with the user, then apply confirmed changes or produce an audit report.
Create a reusable command with explicit preconditions, numbered actions, checks after each step, and error handling. This template provides a structure to customize so Claude verifies the required context before starting a defined workflow.
Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.
Sort open GitHub issues by category, risk, inactivity, and possible duplication. Examine selected reports in detail, identify missing information, and prepare comments, labels, or closures for user approval before taking action.
Analyze TypeScript and JavaScript code for reusable design structures known as GoF patterns. Get detection reports, quality scores, and prioritized refactoring suggestions that account for the frameworks and libraries already used in the project.
Create a separate Git working directory for feature development without switching your current branch. The skill checks branch names and ignore settings, prepares dependencies, and starts background checks, with options for separate dependency installation.
Analyze code, database queries, or systems for performance problems involving speed, memory, and frontend file size. Get prioritized recommendations with code examples, expected impact, implementation effort, risks, and a roadmap for improvements.
Analyze changed files and commits before opening a pull request, a proposed code change for review. Identify oversized or unrelated changes, suggest splits, and create a GitHub PR with a summary, description, and checklist.
Clean up Git worktrees, separate working folders for branches, by identifying merged branches and reviewing unmerged ones. Preview deletions, preserve protected branches, and receive a report of removed folders and reclaimed disk space.
Read staged Git changes and suggest a message in Conventional Commits format, a structured way to describe changes. Include a concise subject and relevant details, then request confirmation before creating the commit.
Audit a collection of agent skills for valid settings, clear activation conditions, complete workflows, and required files. Get scores for each target platform, prioritized fixes, and a separate record of whether activation was actually tested.
Trace how AI tooling developed in a Git repository by identifying configuration file origins, monthly commit activity, major changes, and relevant releases. Produce a Markdown report that explains adoption phases and turning points using Git evidence.
Examines project code, development history, tests, and documentation, then asks three focused questions to recommend a combination of AI-assisted development methods, with practical starting steps tailored to the project.
Build an MCP integration skill using a template that reads server-specific reference notes before calling tools. The Sentry example gathers unresolved errors, groups them by likely root cause, and produces a report with investigation suggestions.
Coordinate feature development from product direction through architecture, planning, validation, and implementation. Run the whole workflow or start at a selected stage, with saved decisions, review checkpoints, and a final pull request.
Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.
Organize open pull requests by size, automated check results, inactivity, and overlapping files. Review selected changes in depth, prepare comments for approval, and optionally create separate local working directories for hands-on review.
Polish Korean commit messages drafted by AI into natural developer language. The skill removes stiff wording and literal translations while preserving the stated changes, commit type, scope, issue numbers, and code identifiers.
Review architecture changes in Apache Pinot, focusing on module dependencies, extension interfaces, abstractions, and class placement. Use it to examine changes that cross module boundaries or introduce new plugins and interfaces.
Review Apache Pinot changes for concurrency and state safety, including locks, shared callbacks, lifecycle changes, and distributed metadata. Use it to examine how changes affect shared state when multiple operations run at the same time.
Compare baseline and current Pinot benchmark results from JMH, a tool for measuring code performance. The skill uses a separate baseline worktree, a working directory kept apart from the current code.