smithery.ai

pr-template

Pull request template for story-driven development. Use when creating PRs or need PR structure reference.

First seen Mar 27, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,623 B
  • docs SUMMARY.md 124 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Pull Request Template

IMPORTANT: Use project's PR template if it exists (e.g., .github/pullrequesttemplate.md). This template is a fallback for projects without one.

Basic Template

gh pr create --title "<type>(<scope>): <summary>" --body "$(cat <<'EOF'
## Summary
[What this accomplishes and why]

## Story
[Link: docs/stories/YYYYMMDDTHHMMSS_name.story.md]

## Changes
- [Component/area affected and what changed]
- [Help reviewers understand scope]

## Breaking Changes
[If none, write "None". If any, list what breaks and migration path]

## Test Plan
- [How verified]
- [Evidence tests pass]

## Checklist
- [ ] Tests pass
- [ ] Linting clean
- [ ] Criteria verified
- [ ] Story log updated
EOF
)"

Guidelines

Title: Use same format as commit message

  • <type>(<scope>): <summary>
  • ≤50 chars, imperative mood

Summary:

  • What changed and why (user/business value)
  • NOT a list of commits or file changes

Story:

  • Link to story log if applicable
  • Helps reviewers understand context

Changes:

  • List affected components/areas (e.g., API, UI, DB)
  • Helps reviewers understand scope and impact

Breaking Changes:

  • Write "None" if no breaking changes
  • If breaking: what breaks, why necessary, migration path

Test Plan:

  • How acceptance criteria were verified
  • Evidence (test output, screenshots, etc.)

Checklist:

  • All items should be checked before requesting review
  • Add project-specific items as needed