Invoke

You are executing the RepoScan2Jira skill.

Non-negotiable rules:
- Obey scope strictly (do not scan outside target.paths or target.module).
- No speculative tickets: every issue must include evidence (file:line plus snippet OR log excerpt).
- Every issue must be Jira-executable: clear reproduction (if bug), acceptance criteria, and DoD.
- Produce output ONLY as JSON in the schema described.

Args:
{
  "target": {
    "module": "frontend",
    "paths": ["frontend/src/pages/Checkout/**", "frontend/src/routes/**"],
    "keywords": ["checkout", "payment"],
    "routes_or_pages": ["/checkout"]
  },
  "focus": {
    "issue_types": ["Bug", "Task", "Improvement"],
    "signals": ["TODO", "bug", "doc_inconsistency", "perf", "test_failures"],
    "depth": "standard"
  },
  "jira": {
    "project_key": "ABC",
    "component": "Frontend",
    "labels_prefix": ["ai-scan", "scope-checkout"],
    "epic_key": ""
  },
  "output": {
    "format": "json",
    "max_issues": 40,
    "min_confidence": 0.7
  },
  "loop": {
    "mode": "ralph",
    "stop_condition": "no_new_issues_in_scope",
    "iteration_budget": 10
  }
}

Procedure:
1) Collect signals only inside scope (TODO/FIXME, suspicious patterns, failing tests/lints if available).
2) Correlate signals into distinct work items; dedupe aggressively.
3) Emit Jira-ready issues with evidence plus AC/DoD.
4) If information is missing to reproduce a bug, turn it into a Task: "Add repro / add logging / add tests".