Loading...
Loading...
Found 466 Skills
Use when executing implementation plans with independent tasks in the current session
Use when analyzing PR review comments to determine relevance, identify ambiguities, and generate a comprehensive report without making code changes. Useful for understanding feedback landscape and initiating collaborative Q&A discussions about unclear or potentially outdated comments.
Autonomous TDD development loop with parallel agent swarm, category evolution, and convergence detection. Use when running autonomous game development, quality improvement loops, or comprehensive codebase reviews.
List my pull requests in the current repository
Read open review comments and resolve them by making code fixes
Enforces Intent UI component library conventions. Use when writing React components, reviewing UI code, or building pages/features that involve UI elements. Ensures semantic color tokens, proper icon usage, correct form patterns, and that existing components from src/components/ui/ are used.
Phase 2 of the issue process — Read the issue report + read the code, identify the true root cause and assess the repair risk, and finally provide the user with 2-3 repair plan options for them to decide. This phase is **not about starting to modify code** — after analysis, show the conclusion to the user first, and only proceed to Phase 3 after the user confirms the plan. The prerequisite dependency easysdd-issue-report has been completed. Trigger scenarios: The user says "analyze this bug", "find the root cause", "locate the issue", and the {slug}-report.md already exists in the issue directory.
Delegate coding, review, diagnosis, planning, structured output, and native browser research tasks to independent Codex sessions via Codex CLI. Use cases include creating new tasks with `codex exec`, resuming multi-turn sessions with `codex exec resume`, performing read-only reviews with `codex exec review`, as well as scenarios requiring `--json` event streams, `-o` final message persistence, image input, or Computer Use browser operations.
Drive a PR to mergeable state — check CodeRabbit and reviewer comments, address valid ones, reply and resolve invalid ones, fix CI failures (even pre-existing ones from main), push fixes, then loop every 4.5 minutes until two consecutive clean checks. Use after opening a PR when you want it babysitted to green.
Full task lifecycle: create → assign → monitor → review → reject/complete. Use when asked to "add a feature", "fix a bug", "create a task", "加个功能", "修个 bug", or "/ak-task <description>".
Run the SPARC Refinement and Completion phases — review code, improve test coverage, validate against specification, and generate documentation
Create Pull Requests following best conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review.