Smithery Logo
MCPsSkillsDocsPricing
Login
Smithery Logo

Accelerating the Agent Economy

Resources

DocumentationPrivacy PolicySystem Status

Company

PricingAboutBlog

Connect

© 2026 Smithery. All rights reserved.

    kecbigmt

    pr-template

    kecbigmt/pr-template
    Communication
    2 installs

    About

    SKILL.md

    Install

    Install via Skills CLI

    or add to your agent
    • Claude Code
      Claude Code
    • Codex
      Codex
    • OpenClaw
      OpenClaw
    • Cursor
      Cursor
    • Amp
      Amp
    • GitHub Copilot
      GitHub Copilot
    • Gemini CLI
      Gemini CLI
    • Kilo Code
      Kilo Code
    • Junie
      Junie
    • Replit
      Replit
    • Windsurf
      Windsurf
    • Cline
      Cline
    • Continue
      Continue
    • OpenCode
      OpenCode
    • OpenHands
      OpenHands
    • Roo Code
      Roo Code
    • Augment
      Augment
    • Goose
      Goose
    • Trae
      Trae
    • Zencoder
      Zencoder
    • Antigravity
      Antigravity
    ├─
    ├─
    └─

    About

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

    SKILL.md

    Pull Request Template

    IMPORTANT: Use project's PR template if it exists (e.g., .github/pull_request_template.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
    Recommended Servers
    Astro Docs
    Astro Docs
    Postman
    Postman
    Google Slides
    Google Slides
    Repository
    kecbigmt/cc-plugins
    Files