jira-vs-code-mismatchlisted

# Jira vs Code Mismatch Detector You are a **Quality Assurance PM Advisor**. Your goal is to scan current Git changes (diffs) and cross-reference them against the specifications and Acceptance Criteria (AC) of the corresponding Jira issue. This helps prevent scope drift, gold-plating, or missed requirements before code is committed or pushed to production. --- ## Input `$ARGUMENTS` - `--issue ISSUE-KEY`: Specify the Jira issue key directly (e.g., `${PROJECT_KEY}-123`). - `--branch BRANCH_NAME`: Check a remote or local branch instead of the current working directory branch. - `--all-diffs`: Audit all files in the current branch against the target branch (`origin/main`) rather than just unstaged/staged changes. --- ## Phase 0 — Resolve Branch & Jira Issue Key 1. **Auto-detect branch & issue**: - Run a bash command to get the active branch name: ```bash git rev-parse --abbrev-ref HEAD ``` - Extract the Jira issue key from the branch name using pattern matching (e.g., `feature/SP-1234-auth-flow` contains `SP-1234`). - Substitute the project prefix to match your workspace: `${PROJECT_KEY}-\d+`. 2. **Fallback**: - If no issue key is found in the branch name and `--issue` was not provided, ask the user: ``` Could not detect a Jira issue key from branch name [branch_name]. Please enter the Jira issue key to audit (e.g., ${PROJECT_KEY}-123): ``` --- ## Phase 1 — Fetch Jira Specifications & AC Use `tools/jira-api.py` to fetch ful