skill: classify by intent first, not by commit/uncommit alone

[charankamarapu]

Summary

Replace the "uncommitted edit → Case 1 mandatory" gate with a symmetric intent check that applies to BOTH committed and uncommitted source changes on the failing handler's path.

Why

Validation runs against cursor-agent --print repeatedly misclassified scenarios:

• Uncommitted regression (S1) — model saw the working-tree edit, framed it as "your source change", and went Case 2b (patch the mock) to "preserve" it. Wrong: the uncommitted edit IS the bug.
• Committed intentional change (S4 mid-iteration) — model saw the commit message, jumped straight to Case 2b-patch without confirming the change was the intended new contract.

The literal rule was correct, but the two-bucket framing (uncommitted = revert, committed = mock) gave the model a permission gradient that flipped its decision on the wrong axis. It rationalized either way based on commit state instead of intent.

What changes

Before:

Any uncommitted edit touching the failing handler's source → Case 1, mandatory. Revert (or ask the dev); do NOT proceed to commit-history reasoning.

After:

Any code change on the failing handler's path — committed OR uncommitted — check intent FIRST, then classify. Was the change EXPECTED (intentional contract change) or UNEXPECTED (regression)? ...ASK THE DEV in one short question and stop. Once intent is known: expected → Case 2 (fix test data on the branch); unexpected → Case 1 (revert the source change). Never patch a mock to "preserve" an uncommitted edit without confirming intent...

Key shifts:

• Symmetric treatment of committed + uncommitted
• Explicit intent question when the diff doesn't decide
• Bans the "preserve your source change" failure mode by name
• Frames the asymmetry (revert is cheap; bad mock patch silently ships regressions)

Test plan

• Synced from the live .cursor/skills/keploy/SKILL.md in the test-12 workspace
• Verbatim-quote probe confirms the new wording reaches the model's context
• Re-run S1-S7 against cursor-agent post-merge — expect Case 1 vs Case 2 classification by intent, not commit state

🤖 Generated with Claude Code