ai-essentials

Critically review all code changes on the current branch against the base branch, identify improvement opportunities across naming, structure, DRY/KISS/YAGNI, declarative style, self-documenting code, edge cases, testing, and general best practices, then produce a categorized refactoring plan with prioritized action items. Use when the user asks to review, clean up, or refactor branch changes, or mentions "refactor plan", "code quality review", or "clean up this branch".

Become the maximum expert on a topic, codebase, or architecture before producing any output. Reads a primary source folder (docs/specs), validates against secondary source folders (code), produces a structured report, and asks clarifying questions when something is unclear. Use when the user says "become the expert", "deep dive into", "research the architecture", "understand this codebase", "load context from", "explore in depth before doing anything", or any time a non-trivial task starts from a folder of docs or a new codebase area.

Generate well-formatted GitHub issue content from a brief context, feature request, or bug report. Outputs ready-to-copy Markdown — does not create the issue. Use when the user asks to write a GitHub issue, draft an issue, create issue content, or mentions "gh issue".

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree before any code is written. Use when the user says "grill me", "roast me", "ask me until we agree 100%", "stress-test this plan", "interview me", "ask me clarifying questions", "iterative process", or any time the user invites questioning before producing output. Also use proactively when a non-trivial design or plan task is starting and significant ambiguity is visible.

Creates pull request descriptions using a fixed template with a concise title, a mixed paragraph-and-bullets summary section, and testing bullets, and can create the PR with gh. Use when the user asks to write a PR description, PR body, pull request summary, or to create a PR.

Triage PR review comments — decide whether to accept or push back on each one. Given comment links from a GitHub PR, fetches comment content and PR diff, then reasons about each comment in context. Uses a personal voice profile for suggested replies — swap skills/shared/pr-review-voice-marco.md for your own. Use when the user shares PR comment links, asks "should I accept this feedback", or wants help responding to PR review comments.

Review a GitHub pull request by URL using the review-team skill. Outputs copy-pasteable conventional comments with line references and code suggestions. Uses a personal voice profile by default — swap skills/shared/pr-review-voice-marco.md for your own. Use when the user shares a PR URL, asks to review a PR, or mentions "review pr".

Launch a team of 6 specialized code reviewers in parallel to catch issues from multiple perspectives. Use when the user says "review team", "comprehensive review", "multi-perspective review", or wants a thorough multi-angle review of branch changes or a plan.