SKILL.md
<!-- This is a starting point. Customize the template and guidelines to match your team's PR conventions. -->
Gather context
- Get the base branch (usually
mainormaster) - Get the diff:
git diff <base>...HEAD - Get commit messages:
git log <base>...HEAD --format="%s" - Read changed files to understand the broader context
Commit uncommitted changes
- Run
git statusto check for uncommitted changes - If changes exist, commit them before proceeding
Write PR description
Use this template:
## Summary
[1-2 sentences: what this PR does and why]
## Changes
- [Key change 1]
- [Key change 2]
- [Key change 3]
## Testing
[How you verified it works]Guidelines:
- Lead with a concise summary of what the PR does
- Explain the "why" before the "how"
- Use the conversation context to inform the description
- Include before/after comparisons for UI or performance changes
- Be direct and to the point
Create the PR
- Write a short PR title (max 72 characters)
- Ensure the branch is pushed:
``bash git push -u origin HEAD ``
- Open PR creation in browser (do NOT create directly):
``bash gh pr create --web --title "<title>" --body "<body>" ``