reopen
The reopen action undoes fixed or skipped marks, returning issues to pending status.
Request
Section titled “Request”{ "action": "reopen", "fps": ["88d32cab35478753"]}Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
fps | array | Yes | Array of fingerprints to reopen |
Response
Section titled “Response”{ "reopened": 1, "prog": {"total": 136, "fixed": 114, "skip": 2, "rem": 20}}Response Fields
Section titled “Response Fields”| Field | Description |
|---|---|
reopened | Number of issues reopened |
prog | Updated progress summary |
Use Cases
Section titled “Use Cases”Undo Accidental Mark
Section titled “Undo Accidental Mark”Marked the wrong issue? Reopen it:
{"action": "reopen", "fps": ["88d32cab35478753"]}Revisit Skipped Issues
Section titled “Revisit Skipped Issues”Previously skipped as false positive, but now want to fix:
{"action": "reopen", "fps": ["xyz1234567890abc", "abc6789012345def"]}Re-examine After Discussion
Section titled “Re-examine After Discussion”User decided an issue needs fixing after all:
{"action": "reopen", "fps": ["88d32cab35478753"]}// Issue returns to pending, will appear in next `next` callExample
Section titled “Example”Agent: sheriff done fps=["88d32cab"] status="skip" → Marked as skipped (thought it was false positive)
User: "Actually, that's a real bug. Can you fix it?"
Agent: sheriff reopen fps=["88d32cab"] → Issue is now pending again
Agent: sheriff next → Issue appears in next batchError Cases
Section titled “Error Cases”| Error Code | Cause | Solution |
|---|---|---|
SARIF_NOT_LOADED | No SARIF file has been loaded | Call load first |
INVALID_FINGERPRINT | Fingerprints are missing or none exist | Provide valid fingerprints from next response |
ALREADY_OPEN | None of the provided issues are marked | Issues are already in pending state |
DB_ERROR | Database error occurred | Check .sheriff/ directory permissions |