review-changes
Review code changes in two modes: local branch review or PR review.
Usage:
/review-changes— Compare current branch againstmain(solo review)/review-changes <branch>— Compare current branch against specified branch (solo review)/review-changes --team— Compare current branch againstmainwith a team of 8 specialist agents/review-changes --team <branch>— Compare against specified branch with a team/review-changes <PR-number>— Review PR in current repo (solo review)/review-changes <PR-number> <owner/repo>— Review PR in specific repo (solo review)/review-changes <PR-URL>— Review PR by URL (solo review)- Add
--teamto any command above to spawn a specialized review team instead of reviewing solo - Add
--headlessto any command above for fully autonomous execution (a challenger agent validates findings instead of asking the developer)
Instructions:
-
Parse arguments and determine mode:
Scan
$1,$2,$3for flags (--team,--headless). The first non-flag argument is the target argument; the second non-flag argument (if any) is the extra argument (used asowner/repoin PR mode).
More from morphet81/cheat-sheets
translate-pdf
Translate a PDF document from one language to another. Extracts text to structured Markdown, translates it, and builds a new translated PDF. Requires a Python environment with pymupdf, markdown, and weasyprint.
80create-jira-ticket
Create a JIRA ticket from user instructions via acli. Uses project from the current branch when possible, lists project epics, recommends the best epic, asks confirmation before creating, uses ADF descriptions, and can attach Figma designs via the Jira integration.
80localise
Generate an HTML translation helper page for Lokalise. Use when the user provides English text (singular/plural) and wants translations across all 23 supported languages, rendered as an interactive HTML page with copy buttons. Triggers on phrases like "translate for Lokalise", "generate translations", "translation table", or when the user provides English strings and mentions languages/i18n/localization.
79update-jira-ticket
Compare the JIRA ticket description to changes made in the current branch and propose description edits and/or comments to keep the ticket accurate and well-documented.
79verify-test-cases
Verify test cases in all test files modified since branching out from base branch. Checks that test cases make sense, have no duplications, and provide meaningful coverage. Spawns parallel agents for multi-file analysis. After the user confirms test-case changes, runs coverage (npm test:coverage or Jest/Vitest fallback) and fixes tests until coverage passes.
79merge-base-branch
Select base branch (from .agent, git history, or main), fetch, stop if already up to date, commit all WIP, merge, resolve conflicts, then lint, tests at 100% coverage, and build—with commits after each fix phase.
79