new-branch-and-pr
Create a fresh branch, complete work, and open a pull request
- License 许可
- MIT
- 最近更新
- 2026-10-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- new-branch-and-pr
- description
- Create a fresh branch, complete work, and open a pull request
03 SKILL.md 正文
New branch and PR
Trigger
Starting work that should be shipped through a clean branch and pull request workflow.
Workflow
- Ensure the working tree is clean or explicitly handled.
- Create a descriptive branch from the latest main.
- Complete implementation and tests.
- Commit focused changes and push.
- Create a concise PR with summary and test notes.
Guardrails
- Keep branch scope focused on one change set.
- Include verification notes before requesting review.
Output
- New branch name
- PR summary and test notes
- PR URL
04 同仓库更多 Skills
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
unslop
Cut AI tells from any writing. Must always apply.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.