Skills backend-pr-workflow

📦

backend-pr-workflow

Name: backend-pr-workflow
Author: DiversioTeam

Content revision r1 High Risk ⚙️ External commands

Review Backend PR Workflow

Backend PRs can miss branch rules, ticket links, release steps, or migration safety checks. This skill gives Claude, Codex, and Claude Code a structured checklist for safer Django backend reviews.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "backend-pr-workflow" from https://skillstore.io/skills/diversioteam-backend-pr-workflow.md and its manifest at https://skillstore.io/api/skills/diversioteam-backend-pr-workflow/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/diversioteam-backend-pr-workflow.md Signed manifest GET /api/skills/diversioteam-backend-pr-workflow/manifest Signed lockfile GET /api/skills/diversioteam-backend-pr-workflow/lockfile

Test it

Using "backend-pr-workflow". Review a backend PR with branch feature/auth-cleanup and title Auth cleanup.

Expected outcome:

What is aligned: The description explains the code change.
Needs changes: [BLOCKING] Rename the branch to start with the ClickUp ticket ID.
Needs changes: [BLOCKING] Update the PR title to begin with the ticket ID.

Using "backend-pr-workflow". Review a migration that adds a non-null field with a default on a large table.

Expected outcome:

What is aligned: The PR calls out the schema change.
Needs changes: [BLOCKING] Split the migration into a nullable add, default setup, and batched backfill.
Needs changes: [SHOULD_FIX] Document the deployment order and rollback plan.

Using "backend-pr-workflow". Review a hotfix targeting release.

Expected outcome:

What is aligned: The PR clearly describes the production issue.
Needs changes: [BLOCKING] Target master for the hotfix if it must bypass release.
Needs changes: [BLOCKING] Add a plan to merge the deployed fix back into release.

Security Audit

High Risk

v10 • 7/9/2026 Open versioned report

Most static findings are false positives caused by markdown inline code and examples, not executable shell or Ruby backtick usage. No prompt injection or automatic command execution was found. One semantic issue remains: the skill should not recommend Slack as a channel for sharing secrets.

Files scanned

432

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

High

SKILL.md:203-204

Unsafe secret-sharing guidance

The skill tells PR authors to include required secrets or setup information and to share secrets via "1Password / Slack". Slack should not be presented as a normal channel for secrets because messages can persist in chat history and broaden access.

The text explicitly names secrets and Slack in the same sharing guidance. It is prose-level risk rather than exposed credential material, so confidence is high but not absolute.

Audited by: claude View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/diversioteam-backend-pr-workflow/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/diversioteam-backend-pr-workflow/security.svg)](https://skillstore.io/skills/diversioteam-backend-pr-workflow?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/diversioteam-backend-pr-workflow?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/diversioteam-backend-pr-workflow/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/diversioteam-backend-pr-workflow.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

DiversioTeam. (2026). backend-pr-workflow security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/diversioteam-backend-pr-workflow/audits/10

BibTeX citation

@techreport{diversioteam-diversioteam-backend-pr-workflow-2026,
  author = {DiversioTeam},
  title = {backend-pr-workflow security audit report (audit version 10)},
  institution = {Skillstore},
  year = {2026},
  number = {10},
  url = {https://skillstore.io/skills/diversioteam-backend-pr-workflow/audits/10},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "backend-pr-workflow security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
  - name: "DiversioTeam"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/diversioteam-backend-pr-workflow/audits/10"
identifiers:
  - type: other
    value: "skillstore:diversioteam-backend-pr-workflow:audit:10"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Prepare a backend PR

Check planned branch name, title, description, and migration summary before opening a pull request.

Review migration safety

Identify Django schema changes that may lock large tables or break running workers during deploy.

Validate release and hotfix flow

Confirm target branches, release titles, tags, and merge-back plans match the expected workflow.

Try These Prompts

Basic PR check

Use backend-pr-workflow to review this backend PR. Branch: <branch>. Base: <base>. Title: <title>. Description: <description>.

Migration review

Use backend-pr-workflow to review these Django model and migration changes for downtime risk. Include blocking and should-fix items.

Hotfix workflow check

Use backend-pr-workflow to check this hotfix plan. Verify the base branch, title, deploy steps, tag plan, and merge-back plan.

Full release readiness review

Use backend-pr-workflow to perform a full release readiness review. Check included tickets, version bump, release PR title, tag plan, migrations, and deployment notes.

Best Practices

Provide the branch name, base branch, PR title, description, and migration summary together.
Include table size and deploy order when asking about migration safety.
Treat blocking findings as required workflow corrections before merge.

Avoid

Do not use the same ClickUp ticket across multiple repository PRs.
Do not combine code removal and schema deletion in one risky deploy.
Do not ask for a full review without providing PR context or migration details.

Frequently Asked Questions

Does this skill run migrations or modify code?

No. It reviews plans and repository context, then provides structured workflow guidance.

Can it review hotfixes?

Yes. It checks hotfix target branches, release titles, tags, and merge-back expectations.

Is it only for Django projects?

The strongest checks are for Django backend repositories, especially migrations and schema deployment safety.

Does it require ClickUp?

The branch and PR naming rules assume ClickUp custom ticket IDs. Other teams may need to adapt those rules.

What output should I expect?

Expect a short summary, aligned items, and tagged needs-change items such as blocking, should-fix, and nit.

Can it replace a human reviewer?

No. It helps catch workflow and migration risks before human review, but it does not approve production changes.

Developer Details

Author

DiversioTeam

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/DiversioTeam/agent-skills-marketplace/tree/main/plugins/backend-pr-workflow/skills/backend-pr-workflow

Ref

1ffa7643651792ccb4bd3b15d924d2c97edff755

Maintenance freshness

7/18/2026

Usage

6 downloads · 281 views

File structure

Review GitHub Pull Requests with CLI Utilities

by Bind

Pull request reviews require repeated eligibility checks, guideline discovery, and precise feedback. This skill documents a consistent CLI workflow for those tasks.

Coding & Development View

backend-pr-workflow

Install with my Agent

Agent-readable resources

Test it

Security Audit

Confirmed security concerns (1)

Risk Factors

Copy report link

Markdown badge

HTML badge

Embed card

APA citation

BibTeX citation

CITATION.cff

Skillstore Score

What You Can Build

Prepare a backend PR

Review migration safety

Validate release and hotfix flow

Try These Prompts

Best Practices

Avoid

Frequently Asked Questions

Developer Details

More from DiversioTeam

bruno-api

code-review-digest-writer

monty-code-review

mixpanel-analytics

pr-description-writer

backend-ralph-plan

Related Skills

code-reviewer

senior-backend

api-design

code-review

convex-create-component

github-pr