Loading...
Loading...
Found 1,173 Skills
Comprehensive iOS/SwiftUI code review with optional parallel agents
Comprehensive Elixir/Phoenix code review with optional parallel agents
Comprehensive security code review workflow for a target repository, producing a markdown report with findings and recommendations.
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.
Review existing code, diffs, branches, or pull requests using concern-specific reviewer personas and evidence. Use when auditing someone else's work, triaging risk in a PR, or producing a ship-it / needs-review / blocked verdict. Do not use to verify your own completed change; use `verify` for that.
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.
Run a formal, multi-dimensional code review of a pull request. Reads the PR diff, classifies change types, dispatches parallel reviewers by dimension (correctness, consistency, docs-sync, plus conditional security/edge-cases/UX/performance/structure/maintainability), and synthesizes findings into an actionable punch list. Use when the user asks to review a PR, run /deep-review, mark a PR as ready for review, or requests a formal/thorough code review.
Analyzes git commits and changes within a timeframe or commit range, providing structured summaries for code review, retrospectives, work logs, or session documentation.
Detects framework-specific anti-patterns, convention violations, and idiom misuse across PHP/Laravel, React/Next.js, and Python/Django/FastAPI codebases. Loads framework-specific reference guides and checks against framework conventions. Generates severity-scored findings with copy-pasteable fix prompts. Trigger phrases: "framework review", "framework check", "laravel best practices", "react best practices", "framework audit", "framework-specific review".
Review Go implementations against spec acceptance tests. References go-conventions and agent-conduct.
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>".
Iterative self-review loop after implementing a plan. Re-read changed code with fresh eyes, fix issues found, re-run quality checks, repeat until clean. For UI work, includes visual verification (view the rendered page). Use after evanflow-executing-plans completes; on success, report and stop — the user decides what's next.