Loading...
Loading...
Found 1,193 Skills
Perform comprehensive, deep analysis of a system and its subsystems to identify bugs, race conditions, stale documentation, dead code, and correctness issues. Use when asked to "audit this system", "exhaustive analysis of X", "analyze for correctness", "root out issues in...", "deep dive into...", "verify this code is correct", "find bugs in...", or when reviewing agent-written code for production readiness. Automatically decomposes systems into subsystems, applies appropriate analysis checklists, and produces structured findings with severity classification.
Systematic code refactoring while preserving all external behavior. Use when identifying code smells, planning refactoring sequences, executing safe structural improvements, or validating behavior preservation. Includes code smell catalog (reference.md) and refactoring execution protocol.
Use when working with comprehensive review full review
Universal code quality rules. Extends nothing — this is the base skill every project should include. Use when writing or reviewing any code.
Test coverage, code quality, defect metrics, and QA KPIs
Remove AI code slop
AI-powered systematic codebase analysis. Combines mechanical structure extraction with Claude's semantic understanding to produce documentation that captures not just WHAT code does, but WHY it exists and HOW it fits into the system. Includes pattern recognition, red flag detection, flow tracing, and quality assessment. Use for codebase analysis, documentation generation, architecture understanding, or code review.
Ensure that Java types are documented with Javadoc comments and follow best practices for documentation.
Defense-in-depth verification before declaring any task complete. Run tests, check build, validate changed files, verify no regressions. Applies 4-level adversarial artifact verification (EXISTS > SUBSTANTIVE > WIRED > DATA FLOWS) with goal-backward framing. Use before saying "done", "fixed", or "complete" on any code change. Use for "verify", "make sure it works", "check before committing", or "validate changes". Do NOT use for debugging (use systematic-debugging) or code review (use systematic-code-review).
Execute a comprehensive Flutter Project Health Audit. Analyzes tech stack, architecture, state management, testing, code quality, CI/CD, and documentation. Produces a Google Docs-ready report with section scores and weighted overall score. Use when the user asks to audit a Flutter project, run a health check, evaluate project quality, or assess technical debt. Triggers on: 'flutter audit', 'health audit', 'project audit', 'flutter health', 'tech debt assessment', 'project quality check'.
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.
Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs. Use when reviewing or finishing a spec-driven change and resolving mismatches between checked-in specs and implementation.