Agent skill · software engineering · aiskillstore
backend-pr-workflow
Pedantic Diversio backend dev workflow Skill that enforces ClickUp-linked branch/PR naming, PR hygiene, safe Django migrations, and downtime-safe schema changes for Django4Lyfe-style backends.
Why this skill is useful
Adds specific branch naming conventions and PR hygiene checks for Django projects that the AI wouldn't reliably generate on its own.
What it needs
About 9k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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 [SHOULDFIX] 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 sections: What’s aligned – bullets of things that follow the workflow. Needs changes – bullets with severity tags: [BLOCKING] – must fix before merge or deploy. [SHOULDFIX] – important but not strictly blocking for merge. [NIT] – minor consistency or documentation suggestions. Each bullet in Needs changes should: Point to the specific item (branch name, PR title, description, migration file, release plan). State the problem and the concrete correction the author should make. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/backend-pr-workflow