Loading...
Loading...
Found 7 Skills
Design and execute tests for an approved DevFlow Spec only when explicitly invoked by the user or precisely delegated by the Planner; maintain an acceptance traceability matrix; complete feature, contract, integration, E2E, regression, and real-scenario verification; output a test report and defect evidence bound to the Commit SHA; do not modify production code.
Acts as the sole DevFlow Planner only when explicitly invoked by the user or precisely routed after entry preparation is complete; responsible for requirements, repository takeover, Spec, Task DAG, global state, coordination, and merging; does not write production code, and is not used for explanation, general advice, or mere documentation editing.
Only when explicitly invoked by the user or precisely delegated by the Planner, implement a single DevFlow Task that has already passed planning and test review, or a Defect that has been attributed as an implementation issue; follow the original repository style, source branch, allowed paths, and change budget, add necessary tests and submit verification evidence, and do not take responsibility for review or merge.
Independently review DevFlow's repository baseline, Spec, test plan, code commits, or release readiness only when the user explicitly invokes it or Planner precisely delegates; output structured conclusions based on file and version evidence, without modifying reviewed artifacts or implementing functionality.
Actively use when the user requests software development, bug fixing, project continuation, refactoring, migration, or infrastructure changes; first confirm the host, installation scope, and same-source integrity, supplement the DevFlow Skill and the current platform's native roles as needed, and then continuously route four-role delivery. Explanations, general advice, standalone review or testing, documentation-only changes, and minimal risk-free edits do not start the full process.
Bug Fixing Skill - Read bugs/pending.csv to select bugs and automatically execute the 8-stage repair process
This skill should be used when reviewing pull requests, performing comprehensive code review, analyzing code changes before merge, or when the user asks for thorough/ultra-critical code review. Performs EXTREMELY CRITICAL 6-pass analysis identifying runtime failures, code consistency issues, architectural problems, environment compatibility risks, and verification strategies. Posts structured review as GitHub PR comment. Use when user asks to "review PR", "review this code", "review changes", "check this PR", "analyze PR", "post review", or for Phase 3 of devflow. Supports parallel review mode with multiplier (code-review-3, code-review 6X) for consensus-based reviews. This is an ultra-critical reviewer that does not let things slip and desires only perfection.