Loading...
Loading...
Found 139 Skills
This skill should be used when the user requests actions such as 'review code', 'do a code review', 'review my branch', 'review MR !1234', or 'review PR'
Creates test strategy and ATDD scenarios.
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or the loop cap is reached. Use when: implementing features from a spec or plan, hardening existing code, fixing a batch of issues, or any multi-file task that benefits from a build-verify-fix cycle.
Focus testing effort on highest-risk areas using risk assessment and prioritization. Use when planning test strategy, allocating testing resources, or making coverage decisions.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.
Comprehensive GitHub code review with AI-powered swarm coordination
This skill is intended for translating academic texts between Chinese and English. It is activated by keywords such as "翻译", "中译英", "英译中", "translate", "paper translation", "academic writing", or when academic documents (including 论文, 文献, 摘要, paper, abstract, manuscript) require translation that adheres to scholarly rigor and consistent terminology.
Internal skill. Use cc10x-router for all development tasks.
Use this skill at the BEGINNING of any detailed review for consistent structure. Use when starting any detailed review workflow, needing consistent structure for capturing context and findings, ensuring comparable review outputs. Do not use when quick catchup without formal review - use catchup. DO NOT use when: diff-focused analysis - use diff-analysis.
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
Write high-quality bug reports that get fixed quickly. Use when reporting bugs, training teams on bug reporting, or establishing bug report standards.
Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.