Run any Skill in Manus with one click

create-pr

Stars19

Forks6

UpdatedFebruary 23, 2026 at 06:59

Prepare a well-structured pull request with Conventional Commits, Jira key support, clear description, and pre-merge checks. Use when changes are ready for review.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

quanwangniuniu

quanwangniuniu/marketing-simplified

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	create-pr
description	Prepare a well-structured pull request with Conventional Commits, Jira key support, clear description, and pre-merge checks. Use when changes are ready for review.

Create Pull Request

When to Use

User asks to create a PR, open a pull request, or prepare for merge.
User mentions submitting changes for review or linking a Jira ticket to a PR.
Task involves finalizing a branch for code review.

Context

Follow .cursor/AGENTS.md (Git / PR section) and .cursor/rules.md. See README and CICD_README.md for CI/CD and testing details.
Use any user-provided context (Jira key, scope, branch name) in the PR title or description.

Instructions

Prepare branch: Ensure all changes are committed. Use Conventional Commits: feat(scope): ..., fix(scope): .... Include the Jira key when applicable. Push branch to remote; verify it is up to date with main/develop.
Run checks: Run npm run lint and npm run test in frontend/. Run docker compose exec backend pytest from repo root (with stack up). Fix any failures before opening the PR.
Write PR description: Summarize changes clearly. Include context and motivation. List any breaking changes. Add screenshots if UI changed.
Create PR: Use a descriptive title. Add appropriate labels. Assign reviewers. Link related issues or Jira ticket if provided.

PR Checklist

Commits follow Conventional Commits; Jira key included if applicable.
Frontend lint and tests pass.
Backend pytest passes (with coverage if required).
PR description complete; breaking changes called out.
Related issue or Jira ticket linked.

More from this repository

same repository

add-backend-endpoint

quanwangniuniu/marketing-simplified

Implement a new backend API endpoint using the full chain (model, serializer, service, view, url, tests). Use when adding a new resource or action to an existing or new Django app.

2026-02-2319

add-frontend-page

quanwangniuniu/marketing-simplified

Implement a new frontend page and wire it to the backend API (API client, types, route, components, navigation, tests). Use when adding a new screen or feature that talks to the API.

2026-02-2319

code-review-checklist

quanwangniuniu/marketing-simplified

Run a code review against MediaJira standards (thin views/pages, API layer placement, no secrets, error handling, permissions, tests). Use before requesting review or merging.

2026-02-2319

run-tests-and-fix

quanwangniuniu/marketing-simplified

Run the full test suite (backend pytest and frontend lint/test), then systematically fix any failures. Use when verifying changes or after pulling updates.

2026-02-2319

security-audit

quanwangniuniu/marketing-simplified

Perform a security pass aligned with MediaJira standards (no secrets, auth/CORS, input validation, least privilege, credential handling). Use for pre-release checks or when touching auth/sensitive code.

2026-02-2319

name	create-pr
description	Prepare a well-structured pull request with Conventional Commits, Jira key support, clear description, and pre-merge checks. Use when changes are ready for review.

Create Pull Request

When to Use

User asks to create a PR, open a pull request, or prepare for merge.
User mentions submitting changes for review or linking a Jira ticket to a PR.
Task involves finalizing a branch for code review.

Context

Follow .cursor/AGENTS.md (Git / PR section) and .cursor/rules.md. See README and CICD_README.md for CI/CD and testing details.
Use any user-provided context (Jira key, scope, branch name) in the PR title or description.

Instructions

Prepare branch: Ensure all changes are committed. Use Conventional Commits: feat(scope): ..., fix(scope): .... Include the Jira key when applicable. Push branch to remote; verify it is up to date with main/develop.
Run checks: Run npm run lint and npm run test in frontend/. Run docker compose exec backend pytest from repo root (with stack up). Fix any failures before opening the PR.
Write PR description: Summarize changes clearly. Include context and motivation. List any breaking changes. Add screenshots if UI changed.
Create PR: Use a descriptive title. Add appropriate labels. Assign reviewers. Link related issues or Jira ticket if provided.

PR Checklist

Commits follow Conventional Commits; Jira key included if applicable.
Frontend lint and tests pass.
Backend pytest passes (with coverage if required).
PR description complete; breaking changes called out.
Related issue or Jira ticket linked.