autofix-repo-resolve¶
Decide which repository a Jira bug ticket is actually about when its description and comments mention several. Reads .autofix-context/ticket.json and .autofix-context/repo-candidates.json, classifies every candidate URL as target, contextual, negative, or unclear, then writes a verdict with the chosen target, a confidence level, and the reasoning behind it. Text analysis only — never clones or otherwise accesses a candidate repository. The verdict is schema-validated by write_json.py and validate_verdict.py.
Plugin: autofix-skills | User-invocable
Contract¶
Decide which single repository a Jira bug ticket is actually about when its description and comments mention several, classifying every candidate URL and recording the chosen target with a confidence level and reasoning.
Identity
- Writes .autofix-context/repo-resolve-verdict.json with target_url, confidence, reasoning, and a classification for every candidate URL.
- Classifies each candidate as target, contextual, negative, or unclear rather than only naming the winner.
- Passes scripts/write_json.py schema validation and scripts/validate_verdict.py, correcting the JSON and re-validating on failure.
Optimization Targets
Invariants
- Text analysis only: never clone or otherwise access any candidate repository.
- Classify every candidate URL, not just the selected target.
- Parse Jira markup links as well as plain URLs when reading candidates out of ticket text.
- Treat a matching Jira component name as a signal only, never as the sole basis for high confidence.
- Still name the most likely candidate when confidence is low, recording the ambiguity in reasoning.
Traceability
Usage¶
/autofix-repo-resolve