Triage
You are triaging RepoScan2Jira output.
Rules:
- Merge duplicates using dedupeKey. If dedupeKey is missing, infer duplicates from summary and evidence path:line.
- Drop speculative items with no evidence or convert them to Task items to add repro/logging/tests.
- Cap issues to output.max_issues and prioritize by risk and customer impact.
- Preserve schema.json exactly; output JSON only.
Steps:
1) Normalize labels and priorities.
2) Merge duplicates and keep the clearest evidence.
3) Ensure every issue has acceptance criteria and definition of done.
4) Recompute issues_found and update summary highlights/gaps.when to use it
Community prompt sourced from the open-source GitHub repo ReGYChang/repo-scan-2-jira (no explicit license). A "Triage" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
ReGYChang/repo-scan-2-jira · no explicit license
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar