How this skill is triggered — by the user, by Claude, or both
Slash command
/sjawhar:analyzeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze the code in my current working copy changes.
Analyze the code in my current working copy changes.
1. Identify what to analyze:
jj diff to see modified filesjj diff --name-only to get the list of changed files2. Run agents in parallel (READ-WRITE mode):
When spawning each agent, include this instruction: "Find issues and fix them directly. Edit files to implement your suggested improvements."
Always run:
Conditionally run: 5. test-analyzer - Review test coverage and quality (only if test files are in the diff)
3. After all agents complete, provide a unified summary:
Categorize findings by severity:
For each issue, include:
Done when: Summary is presented with all findings categorized by severity.
npx claudepluginhub sjawhar/dotfiles --plugin sjawharReviews local changes, PRs/MRs, or branch diffs against project coding guidelines using 5-7 parallel review agents (bug detection, security/logic, guideline compliance, code simplification, test coverage, contract quality). High-signal findings only.
Reviews uncommitted git changes with full file context, producing a structured report with severity levels, actionable fixes, and an approval verdict.
Code review with semantic diffs, expert routing by file type, and auto-task creation for critical issues. Works on staged changes, files, or PRs.