ruver-create-pr-backendlisted

# Ruver Create PR Backend — Orchestrator Generate a complete, professional PR description for the current backend branch. The command file is the thin entry point; this skill owns the workflow. ``` SETUP → ANALYZE (parallel) → AC RESOLUTION (pt-BR) → WRITE → RENDER ``` ## Tone - **Final description**: English (template fields, bullets, test plan). - **Interactive prompts**: pt-BR. Translate the author's answers into English before writing them into the description. ## Prerequisites - `gh` authenticated only if `$ARGUMENTS` contains a dependent PR URL (to validate it). - Working tree may have uncommitted changes — the skill reads `main..HEAD`, not the index. - Branch has ≥ 1 commit ahead of `main`. --- ## Phase A — Confirm repo and parse argument 1. Confirm we're in `empath-api-v2`: - Look for Elysia in dependencies, `src/modules/v1/` structure, `package.json` name. - If not → stop and print: `This command runs in empath-api-v2. For frontend, use /ruver-create-pr-frontend.` 2. Parse `$ARGUMENTS`: - Empty → `DEPENDENT_PR_URL = null`. - Looks like a GitHub PR URL → `DEPENDENT_PR_URL = <url>`. - Anything else → stop and ask the user (pt-BR) to clarify. ## Phase B — Collect branch context ```bash git rev-parse --abbrev-ref HEAD git log main..HEAD --oneline git log main..HEAD --pretty=%s git diff main...HEAD --stat git diff main...HEAD ``` If `git log main..HEAD` is empty → stop. Print: `No commits ahead of main. Nothing to describe.` Build `branch_conte