Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From code-analysis
Run a PR-aware quality audit. Uses mcp__gitnexus__detect_changes + mcp__gitnexus__impact to identify affected subsystems, then runs Phase 2 quality-analyzer on that subset only. Fast (minutes). Use when the user wants to audit a pull request, working-tree changes, or staged changes before commit. Accepts: `/analyze-pr main..feature`, `/analyze-pr --staged`, `/analyze-pr --working-tree`, `/analyze-pr <commit>..<commit>`. Requires a prior /analyze baseline (Phase 1 must have been completed at least once).
How this skill is triggered — by the user, by Claude, or both
Slash command
/code-analysis:analyze-pr [<git-range>|--staged|--working-tree][<git-range>|--staged|--working-tree]sonnetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Runs a focused quality audit on only the subsystems impacted by a git change set.
Runs a focused quality audit on only the subsystems impacted by a git change set.
mcp__codeanalyzer__get_phase_state. Require: result.phase1.status == "done" (Phase 1 baseline)..codeanalyzer/subsystems.md exists.| Argument form | Behavior |
|---|---|
<base>..<head> | git diff <base>..<head> --name-only |
--staged | git diff --cached --name-only |
--working-tree | git diff --name-only + git ls-files --others --exclude-standard |
<single-ref> | git diff <ref>^..<ref> --name-only (single commit) |
| (empty) | default to --working-tree |
Use the chosen git command. Save to .codeanalyzer/state/pr-scope.json:
{ "ref": "<human-readable>", "files": ["...", "..."] }
For each changed file, call mcp__gitnexus__detect_changes(file=<path>) and/or mcp__gitnexus__impact(target=<file>, direction="downstream"). Collect the set of downstream-affected files.
Total scope = changed files ∪ downstream-affected files (dedup).
Read .codeanalyzer/subsystems.md frontmatter. For each affected file, find its subsystem id. Build:
{ "affected_subsystems": { "s01": ["file1", "file2"], "s03": [...] } }
For each affected subsystem, invoke quality-analyzer with:
{ "pr_scope": { "files": [<this-subsystem-subset>], "ref": "<ref>" } }
Invoke code-analysis:pr-report with { ref, pr-scope, affected_subsystems }. It emits .codeanalyzer/reports/pr/{ref}/*.md.
.codeanalyzer/reports/pr/<sanitized-ref>/
├─ summary.md
├─ changed-symbols.md
├─ impact.md
└─ quality-<subsystem-id>.md (one per affected subsystem)
phase-state.json — this is a lateral workflow."/analyze-pr requires Phase 1 baseline. Run /analyze first.".npx claudepluginhub juyeongyi/jylee_claude_marketplace --plugin code-analysisGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.