backend-pr-workflowlisted

# Backend PR Workflow Skill ## When to Use This Skill Use this Skill whenever you are: - Creating or reviewing a backend PR that touches Django models, migrations, or production data. - Preparing a PR for Django4Lyfe / Workforce backend or a similar repo that uses ClickUp as the primary ticket system. - Planning a release or hotfix and want to ensure the workflow (branches, tags, and migrations) is correct and downtime-safe. If local `AGENTS.md` / `CLAUDE.md` in the target repo conflict with anything here, **treat those files as the source of truth** and use this Skill as the default baseline. ## Example Prompts - “Use the `backend-pr-workflow` skill to review this Django4Lyfe PR’s branch name, ClickUp linkage, migrations, and downtime-safety. Here are the branch name, base branch, and PR title: …” - “Before I open this backend PR, run `backend-pr-workflow` on my planned title, description, and migration summary and tell me all `[BLOCKING]` and `[SHOULD_FIX]` issues.” - “For this hotfix PR on Django4Lyfe, use `backend-pr-workflow` to check that my base branch, title, and release plan follow our backend workflow.” - “I’ve added a new nullable field and a backfill migration. Use `backend-pr-workflow` to verify that my migrations and rollout plan are downtime-safe.” ## Severity Tags & Output Shape When this Skill reviews a PR or workflow plan, the response **must** be structured and tagged: - Start with a 1–3 sentence summary of what was checked. - Then use sectio