SKILL PROCESS

Backend PR Workflow

Pedantic backend PR workflow skill that follows repo-local workflow docs, GitHub issue linkage, safe Django migrations, and downtime-safe schema changes.

Overview

Pedantic backend PR workflow skill that follows repo-local workflow docs, GitHub issue linkage, safe Django migrations, and downtime-safe schema changes.

This skill ships inside the Backend PR Workflow plugin and can be installed through the Claude Code marketplace or directly in Codex from its skill path.

Parent Surface

Parent docs: Backend PR Workflow

Related wrapper commands from the parent plugin:

/backend-pr-workflow:check-pr

When to Use This Skill

Use this Skill whenever you are:

production data.

uses GitHub as the active workflow system.

and migrations) is correct and downtime-safe.

If the target repo has its own harness docs, treat AGENTS.md as the canonical entrypoint and follow any linked workflow/release/migration docs or directory-scoped AGENTS.md files for per-topic truth. CLAUDE.md should be treated as a pointer, not as a unique rule source. This Skill is the default baseline when repo-local docs are absent or thin.

  • 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 GitHub as the active workflow system.
  • Planning a release or hotfix and want to ensure the workflow (branches, tags, and migrations) is correct and downtime-safe.

Example Prompts

  • “Use the backend-pr-workflow skill to review this Django4Lyfe PR’s branch name, linked issues, 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:

Each bullet in Needs changes should:

file, release plan).

Example bullet:

  • 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.
  • [SHOULD_FIX] – important but not strictly blocking for merge.
  • [NIT] – minor consistency or documentation suggestions.
  • 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.
  • [SHOULD_FIX] Branch name 'misc/work' does not match the repo's documented feature-branch convention. Rename it to something clearer like 'feature/1234-user-auth' or 'feature/user-auth'.

Inputs This Skill Expects

Before giving a full review, this Skill should gather:

If any of these are missing or unclear, ask the user to provide them before doing a full workflow review.

Before applying the checklist, inspect the repo harness:

AGENTS.md files when they exist.

[SHOULD_FIX] harness finding recommending a repo-docs update.

  • The repository and context (e.g. Django4Lyfe backend / monolith).
  • The branch name.
  • The PR title and PR description (or the planned ones).
  • The base branch (what the PR targets: release, master, etc.).
  • Whether the PR:
  • Includes Django model changes.
  • Adds, modifies, or deletes migrations.
  • Is a normal feature/bugfix, a hotfix, or a release PR.
  • Read AGENTS.md first.
  • Load linked workflow/release/runbook docs or relevant directory-scoped AGENTS.md files when they exist.
  • If workflow rules are tribal knowledge or only implied by stale docs, emit a [SHOULD_FIX] harness finding recommending a repo-docs update.

Resources

Declared allowed tools:

ReadBashGlobGrep

Installation

Switch between Claude Code and Codex, then copy the install command for the runtime you use.

claude plugin marketplace add DiversioTeam/agent-skills-marketplace
claude plugin install backend-pr-workflow@diversiotech

Invocation:

/backend-pr-workflow:check-pr