- Home
- /
- Categories
- /
- Code Review
Code Review
Automated code review and analysis
using-git-worktrees
by hxk622
"开始需要与当前工作区隔离的功能开发或执行实施计划前使用。创建隔离的 git worktrees,智能选择目录并进行安全验证。Use for feature work isolation or before implementation plans - creates isolated git worktrees with smart directory selection."
pr-message
by milistu
Write a concise, high-signal GitHub pull request message that explains intent, impact, and risk
issue-driven-development
by troykelly
Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification
executing-plans
by hxk622
"当有书面实施计划需要执行时使用,在单独会话中执行并设置审查检查点。Use when you have a written implementation plan to execute in a separate session with review checkpoints. Batch execution with checkpoints for architect review."
spec-reviewer
by EnzeD
Review and challenge spec documents against the project's codebase, best practices, and guidelines. Spawns a team of parallel agents to analyze consistency, code reuse, performance, scope, and testability. Use when the user says "challenge", "review spec", "check spec", "audit spec", or asks to validate a spec file against the codebase. Triggers on spec file paths (e.g., specs/037-hover-brackets-info.md).
ruleset-optimization
by ilude
Guidelines for optimizing Claude rulesets and instruction files (CLAUDE.md, settings.json) using context efficiency principles. Includes strategies for skill extraction, progressive disclosure, token savings calculation, and deduplication. Manually invoke when optimizing rulesets, reducing context size, extracting content to skills, or improving ruleset organization.
multi-agent-ai-projects
by ilude
Guidelines for multi-agent AI and learning projects with lesson-based structures. Activate when working with AI learning projects, experimental directories like .spec/, lessons/ directories, STATUS.md progress tracking, or structured learning curricula with multiple modules or lessons.
swift-patterns
by efremidze
Review, refactor, or build SwiftUI features with correct state management, modern API usage, optimal view composition, navigation patterns, performance optimization, and testing best practices.
session-start
by troykelly
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
least-astonishment
by ilude
Principle of Least Astonishment (POLA) - ensure code changes behave as users and developers expect. Activate when making code changes, refactoring, modifying APIs, renaming functions/variables, changing file structure, or reviewing proposed implementations. Guides predictable, convention-following changes.
receiving-code-review
by hxk622
"接收代码审查反馈时使用,在实施建议之前,特别是当反馈不清晰或技术上有疑问时。需要技术严谨和验证,而不是盲目实施。Use when receiving code review feedback - requires technical rigor and verification, not blind implementation."
review-scope
by troykelly
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
pr-test-analyzer
by troykelly
Use when asked to evaluate PR test coverage or explicitly asked to run the pr-test-analyzer subagent.
agent-debugger
by AvivK5498
Systematic debugging toolkit for AI agentic workflows in customer support. Use when diagnosing issues with AI agents including wrong responses, tool/function calling problems, conversation loops, stuck states, or performance/latency issues. Works with any framework (LangChain, custom agents, Claude API) and accepts conversation logs, API logs, tool execution logs, and agent configurations.
finishing-a-development-branch
by hxk622
"当实现完成、所有测试通过,需要决定如何集成工作时使用。通过展示 merge、PR 或 cleanup 的结构化选项来引导完成开发工作。Use when implementation is complete, all tests pass, and you need to decide how to integrate the work."
gh-fix-ci
by akiojin
Inspect GitHub PR for CI failures, merge conflicts, update-branch requirements, reviewer comments, change requests, and unresolved review threads. Create fix plans and implement after user approval. Resolve review threads and notify reviewers after fixes.
kotlin-fundamentals
by pluginagentmarketplace
Kotlin language fundamentals - syntax, null safety, data classes, extensions
api-documentation
by troykelly
Use when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.
fault-tree-analysis
by ddunnock
Conduct Fault Tree Analysis (FTA) to systematically identify and analyze causes of system failures using Boolean logic gates. Top-down deductive method for safety and reliability engineering. Use when analyzing system failures, evaluating safety-critical designs, calculating failure probabilities, identifying minimal cut sets, assessing redundancy effectiveness, or when user mentions "fault tree", "FTA", "system failure analysis", "minimal cut sets", "safety analysis", "failure probability", "AND/OR gates", or needs to trace failure pathways from top event to basic events. Supports qualitative structure analysis and quantitative probability calculations.
A Prompt Optimizer
by strativd
Transform a user's 'basic prompt' into an 'optimized prompt' by applying context engineering -> the right context beats the right prompt.
branch-discipline
by troykelly
Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base
verification-before-completion
by hxk622
"在声称工作完成、修复或通过之前使用,在提交或创建 PR 之前。需要运行验证命令并确认输出后才能声称成功。证据先于断言。Use when about to claim work is complete - evidence before assertions always."
conflict-resolution
by troykelly
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
security-review
by troykelly
MANDATORY for security-sensitive code changes - OWASP-based security review with dedicated checklist, required before PR for auth, input handling, API, database, or credential code