Validate Pr Description

Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission

PublishedJun 4, 2026

Loading actions...

5 minBeginnerprompt17 files

Skill content

Main instructions and any bundled files for this skill.

markdown

Additional Files (16)

Validate PR Description Command

Context

PR title: [User provides]
PR body: [User provides text or path to a file]

Your task

Validate the PR description against these standards:

1. Conventional Commit Title

Title must match <type>(<scope>)?: <description> where type is one of: feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert.

2. Issue Linking Keywords

Body should contain at least one issue linking keyword: Closes #N, Fixes #N, Resolves #N (and their past-tense variants). These keywords auto-close the linked issue when the PR merges on platforms that support them (GitHub, GitLab). On other platforms (Azure DevOps, Bitbucket), they serve as traceability markers.

3. PR Template Compliance

Check that required sections are populated:

Summary (non-empty)
Changes (at least one item)
Type of Change (at least one checkbox marked)

Validation Script (optional)

If .claude/skills/github/scripts/pr/validate_pr_description.py exists, run it:

uv run python .claude/skills/github/scripts/pr/validate_pr_description.py \
  --title "[title]" \
  --body-file "[path-to-body.md]"

Otherwise, validate manually against the criteria above.

Report findings with actionable recommendations for any failures.

Contents

View Original Source

Related Skills

General

PromptBeginner5 minmarkdown

Untitled Skill

193

Jan 12, 2026

General

PromptBeginner5 minmarkdown

Frontend Typescript Linting.mdc

TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend li...

160

Feb 15, 2026

General

PromptBeginner5 minmarkdown

2. Apply Deepthink Protocol (reason about dependencies

risks

126

Jan 15, 2026