tzachbon/srulik-toolkit / plugins/srulik-toolkit/skills/create-pr
create-pr
VerifiedCreate a pull request for the current changes.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.3 KB |
| references/conventions.md | markdown | 4.8 KB |
| references/evidence.md | markdown | 4.0 KB |
| references/preparation.md | markdown | 2.8 KB |
| references/publishing.md | markdown | 3.9 KB |
references/conventions.md
View on GitHub# Repository conventions
Derive conventions from evidence instead of imposing a preferred house style.
## Evidence order
Use the first source that settles each decision:
1. Repository instructions, contribution docs, PR templates, commit or title linters, CI checks, release rules, and branch protection.
2. A clear repeated pattern across several recent merged PRs from maintainers or code owners.
3. The fallbacks below.
Explicit rules outrank historical practice. A single PR is an example, not a convention. Prefer merged work because it reflects accepted practice; ignore bots, bulk dependency updates, generated releases, and obvious exceptional changes when inferring ordinary authoring style.
Record evidence separately for branch names, commit messages, PR titles, body structure, issue linking, draft status, reviewers, and labels. One observed convention does not establish the others.
## Fallbacks
When repository evidence is insufficient:
- Branch: `<type>/<short-kebab-case-summary>`.
- Commit and PR title: Conventional Commit form, `<type>(optional-scope): <imperative summary>`.
- Use the narrowest accurate type, commonly `feat`, `fix`, `docs`, `test`, `refactor`, `build`, `ci`, or `chore`.
- Keep the summary specific and omit a period.
- Body: `Summary`, `Evidence`, `Merge danger`, and `Blast radius`; add `Why` only when the motivation is not evident. Use the review guidance below to fill them.
- Create a non-draft PR unless the user requested a draft.
- Do not assign reviewers, labels, milestones, or projects without repository evidence or a user request.
## Title and body
Keep both as short as the repository permits. A title names the outcome and why it matters, not the implementation diary:
- Weak: `perf(server): negotiate permessage-deflate on the websocket`
- Better: `perf(server): cut websocket frame size by 70%+ with compression`
Open the body with the problem in the user's terms, then the fix. Do not lead with an inventory of removed functions and touched entry points:
- Weak: "Removed implicit workspace carry-over from every new-thread entry point. Deleted buildContextualThreadOptions and the sidebar seed-context machinery."
- Better: "My new-worktree default was ignored when starting threads from an existing worktree. Now the configured defaults always apply."
End the body with the public model name and harness that made the change, for example `Created with <model> in <harness>.`, including subagent models that wrote part of it. If the harness reports no model name, name only the harness. Follow any attribution line the user or repository requires instead. The body should help a reviewer answer three questions: what changed, why when non-obvious, and what proves it.
When a template exists:
- preserve required headings, checklists, and issue-closing syntax;
- remove untouched instructional comments;
- fill only applicable optional sections;
- mark a checkbox complete only when its condition is true;
- explain a required but inapplicable item briefly instead of falsely checking it.
## Help the reviewer decide
Apply this guidance within the repository's required body structure. Add a missing
section only when the template permits it; otherwise place the information under
the nearest applicable heading.
- **Summary:** describe the concrete trigger and resulting behavior. Invoke
[show-me](../../show-me/SKILL.md) when a small flow, pseudocode sketch, or diff
makes the change easier to review. Scale the visual to the change.
- **Evidence:** use the captured [validation evidence](evidence.md). For a behavior
change, show the same scenario before and after, with exact outcomes and tested
revisions. Label unavailable baseline evidence and remaining coverage honestly.
For UI changes, embed or link the required UI proof in the description, under
this section or the template's nearest applicable heading; a comment alone is
insufficient.
- **Merge danger:** state whether this is a two-way door or a one-way door and why.
A code revert may not undo deleted data, migrations, public actions, or external
side effects. Describe recovery prerequisites when they matter; do not run a
deployment or destructive action just to prove reversibility.
- **Blast radius:** name the affected callers, users, data, or services and the
boundaries supported by inspection or checks. Explain a risk that changes the
review decision; avoid unsupported claims that a change is safe or isolated.
Do not repeat the title, list every changed file, narrate routine commands, add generic benefits, or claim safety, completeness, performance, or compatibility without evidence. Link an issue only when the relationship is verified. Use closing keywords only when merge should close that issue.
The convention gate passes when every outbound naming and description choice has a cited repository source or an explicit fallback.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |