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 rami
Auto-trigger when the user wants to challenge, rebut, or dispute a Rami code review finding — phrases like "rebut this", "this is a false positive", "Rami is wrong about X", or "tell Rami this is intentional". Routes disagreement through the Rami MCP rebuttal protocol instead of a public slash command.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rami:rami-rebut-findingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read and follow @${CLAUDE_PLUGIN_ROOT}/workflows/rami-rebut-finding/SKILL.md.
Read and follow @${CLAUDE_PLUGIN_ROOT}/workflows/rami-rebut-finding/SKILL.md.
This skill is intentionally triggered by natural-language user intent, not by a /rami:* slash command. Use Rami's MCP rebut tool as the only state-changing channel for disputed Rami findings; never reply to or resolve the GitHub review thread as a substitute.
npx claudepluginhub rami-code-review/claude-code-marketplace --plugin ramiGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.