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 ruflo-jujutsu
Git diff analysis with risk scoring and change classification
How this command is triggered — by the user, by Claude, or both
Slash command
/ruflo-jujutsu:jujutsuThe summary Claude sees in its command listing — used to decide when to auto-load this command
Analyze current git changes: 1. Run `git diff` to capture the current diff 2. Call `mcp__claude-flow__analyze_diff` with the diff for comprehensive analysis 3. Call `mcp__claude-flow__analyze_diff-risk` for risk score 4. Call `mcp__claude-flow__analyze_diff-classify` for change type classification 5. Present: risk level, change type, affected files, and reviewer recommendations
Analyze current git changes:
git diff to capture the current diffmcp__claude-flow__analyze_diff with the diff for comprehensive analysismcp__claude-flow__analyze_diff-risk for risk scoremcp__claude-flow__analyze_diff-classify for change type classificationnpx claudepluginhub p/sudeeparyan-ruflo-jujutsu-plugins-ruflo-jujutsu10plugins reuse this command
First indexed May 13, 2026
Showing the 6 earliest of 10 plugins