backend-pr-workflow
Enforce backend PR workflow standards
Backend pull requests often miss critical workflow steps like proper ClickUp ticket linkage, migration safety checks, or downtime-safe schema changes. This skill provides a pedantic checklist to catch these issues before merge and deployment.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "backend-pr-workflow". Review my Django PR. Branch: feature/my-thing. Title: Add user profile. Base: master. I added a required field with default on a large table.
Expected outcome:
- What is aligned: Title includes descriptive text
- [BLOCKING] Branch name feature/my-thing must start with clickup_<ticket_id> for CI to run
- [BLOCKING] PR targets master but should target release for normal feature work
- [BLOCKING] Adding non-nullable field with default on large table causes table rewrite. Use nullable column first, then two-step migration.
Using "backend-pr-workflow". Check my hotfix PR. Branch: clickup_GH-999_crash-fix. Title: [GH-999] Hotfix for payment bug. Base: master. I need to drop the old column and update all queries.
Expected outcome:
- What is aligned: Branch follows naming convention
- What is aligned: Hotfix correctly targets master branch
- [BLOCKING] Removing field and code in same PR causes deployment errors. Split into two PRs: first remove code usage, then drop column.
- [SHOULD_FIX] Update PR description to include rollback plan for this hotfix.
Security Audit
SafePure prompt-based skill containing only SKILL.md documentation. No executable code, scripts, or network calls. All 134 static findings are false positives caused by the scanner misinterpreting documentation patterns (ticket IDs, dates, code formatting, branch names) as security-relevant code patterns. Uses only standard Read, Bash, Glob, and Grep tools as permitted by the AI environment.
Risk Factors
🌐 Network access (1)
⚙️ External commands (99)
Quality Score
What You Can Build
Review Django PRs
Ensure PRs follow naming conventions, migration best practices, and downtime-safe deployment patterns.
Standardize PR workflow
Enforce consistent branch naming, ticket linkage, and release processes across the backend team.
Prevent bad migrations
Catch dangerous schema changes before they reach production and cause downtime.
Try These Prompts
Use the backend-pr-workflow skill to review this PR. Branch: clickup_GH-1234_feature-name. Base: release. Title: [GH-1234] Add new feature.
Run backend-pr-workflow on my planned PR. Title: [GH-785] Fix login bug. Description: Fixes timeout issue. Migration: added is_active field with default True on large User table.
Use backend-pr-workflow to check if my Django migration plan is downtime-safe. I am adding a nullable UUID field to a table with 10 million rows, then backfilling in migration.
Use backend-pr-workflow to validate my hotfix. Target branch: master. Title: Hotfix release: 2025-08-19. This is an emergency fix for production bug.
Best Practices
- Always include the ClickUp ticket ID in branch name and PR title for traceability.
- Use two-step migrations for adding columns to large tables: nullable first, then backfill.
- Split code removal from schema removal into separate PRs to avoid deployment errors.
Avoid
- Merging code that removes a field with the migration that drops it in the same PR.
- Using volatile defaults like UUID or current_timestamp inside atomic migrations on large tables.
- Reusing the same ClickUp ticket ID across multiple repositories for a single feature.