<h1 align="center">
<a href="https://prompts.chat">
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission
Loading actions...
<a href="https://prompts.chat">
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 linting, type safety, or ESLint configuration.
risks
Validate the PR description against these standards:
Title must match <type>(<scope>)?: <description> where type is one of:
feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert.
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.
Check that required sections are populated:
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.