backend-pr-workflow

Enforce ClickUp-linked branch naming and migration safety for Django PRs.

3|4|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/DiversioTeam/agent-skills-marketplace --skill backend-pr-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-pr-workflow
Source: https://github.com/DiversioTeam/agent-skills-marketplace/tree/main/plugins/backend-pr-workflow/skills/backend-pr-workflow
Command: npx skills add https://github.com/DiversioTeam/agent-skills-marketplace --skill backend-pr-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures the backend PR workflow's branch naming, PR hygiene, and safe migration/downtime practices for Django4Lyfe-style backends that use ClickUp tickets.

Core Features & Use Cases

  • Branch naming: Enforces clickup_<ticket_id> prefix on branches.
  • Migration safety: Downtime-safe schema changes and safe rollout plans.
  • PR hygiene: Ensures PR titles, descriptions, and migrations are aligned with tickets and release plans.

Quick Start

Use this Skill to review a planned backend PR: verify branch name, base branch, and migration strategy.

Frequently Asked Questions about backend-pr-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce ClickUp-linked branch naming for Django backend PRs?

Enforce branch naming by prefixing with `clickup_<ticket_id>` on all Django backend PRs. This Skill validates that branches follow this convention and link to active ClickUp tickets, ensuring traceability and alignment with your ticket system before code review.

What makes a Django migration safe for production rollout without downtime?

Safe migrations avoid locking production tables and separate schema changes from data changes across releases. This Skill reviews migration strategy to ensure downtime-safe schema modifications, rollout sequencing, and validates that destructive changes are planned with appropriate release windows.

How do I review backend PR hygiene for Django projects?

Review PR titles, descriptions, and migrations against ClickUp tickets and release plans. This Skill enforces alignment between PR metadata, branch names, and migration safety, catching hygiene gaps before code review and reducing merge conflicts with release workflows.

Can I use this workflow with Django backends that manage production data changes?

Yes, this Skill is designed for Django4Lyfe-style backends using ClickUp tickets and handling migrations or production data changes. It applies specifically to PRs touching models, migrations, or schema—ensuring downtime-safe practices during releases and hotfixes.

What happens if a PR branch doesn't follow the ClickUp naming convention?

The Skill flags branch naming violations in review output, requiring the `clickup_<ticket_id>` prefix. This prevents merging untracked work and ensures every backend change is tied to a ClickUp ticket for audit and release planning.

How does this Skill handle migration safety during hotfixes?

During hotfixes, this Skill validates that migrations are safe for immediate rollout and don't introduce downtime. It reviews schema changes, data migration sequencing, and rollback plans to ensure hotfix PRs can deploy without service interruption.