Loading...
Loading...
Found 1,266 Skills
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.
Go-specific code review with 6-phase methodology: Context, Automated Checks, Quality Analysis, Specific Analysis, Line-by-Line, Documentation. Use when reviewing Go code, PRs, or auditing Go codebases for quality and best practices. Use for "review Go", "Go PR", "check Go code", "Go quality", "review .go". Do NOT use for writing new Go code, debugging Go bugs, or refactoring -- use golang-general-engineer, systematic-debugging, or systematic-refactoring for those tasks.
Turn plans, specs, diffs, and half-confident opinions into something that can survive contact with a real review.
Standards de codage universels, bonnes pratiques et patrons pour le développement TypeScript, JavaScript, React et Node.js.
SOLID principles checklist with Java examples. Use when reviewing classes, refactoring code, or when user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation, or Dependency Inversion.
Checkpoint - Pre-publish review with multi-layer deep analysis. Triggers: Preparing to publish an npm package, requiring pre-release review, or checking code change quality. Review Layers: - Per-Change: In-depth analysis of each change group (up to 10 Agents) - Holistic: Parallel review by 5 roles (Architecture/Development/Testing/Security/Documentation) - Synthesis: 1 Agent summarizes review results Commands: - /把关 - Start pre-publish review - /把关 check - Check unpublished changes - /把关 version - Recommend version upgrade - /把关 report - Generate review report - /review - English command Capabilities: Unpublished change detection, in-depth per-change analysis, multi-role review, version recommendation, release risk assessment.
Reads documented bugs from bugs.md, analyzes root causes, implements fixes with regression tests, and validates the full test suite. Prioritizes fixes by severity (high to low). Updates bugs.md with correction status and generates a final bugfix report. Use when the user asks to fix bugs, resolve issues, or run the bugfix workflow for a feature. Do not use for new feature implementation, code review, or QA testing.
Detect package managers and discover outdated or vulnerable dependencies. Returns structured findings without upgrading. Use when the user asks to "review dependencies", "check for outdated packages", "check dependencies", "scan dependencies", or "dependency review".
Analyzes codebases to identify refactoring opportunities based on Martin Fowler's catalog of code smells and refactoring techniques. Detects duplicated code, high coupling, complex conditionals, primitive obsession, long functions, and other structural issues. Produces a structured refactoring report with prioritized findings saved to docs/_refacs/. Use when auditing code quality, preparing for a refactoring sprint, or reviewing architectural health. Don't use for style/formatting issues, performance optimization, or security audits.
Reviews the feature you just built and adds missing test coverage. Focuses on behavior that matters — not coverage metrics. Use after completing a feature to identify untested code paths, edge cases, and risk areas.
Review the latest changes and check whether they comply with the project's documented guidelines (AGENTS.md, CLAUDE.md, or equivalent). Use when reviewing local diffs, recent commits, or feature work and you need a findings-first assessment of architecture, reuse, testing, and repo-specific rules.
Ultra-compressed PR review comments. One issue per line: Location • Problem • Fix. Remove preambles, prioritize signals. Supports Japanese. Trigger with "PR review please", "code review", "/review", "/genshijin-review". Candidate for automatic activation during pull request reviews.