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/publishing.md
View on GitHub# Provider publication
Publish the prepared change once, then verify provider state.
## Commit and push
- Recheck the intended file set and working state after validation.
- Stage intended paths explicitly. Inspect the staged diff and staged file list before committing.
- Exclude unrelated and incidental generated files. Never use a blanket stage when the worktree contains unrelated changes.
- Commit only when intended uncommitted changes exist. Use the convention selected earlier and ensure the commit contains the validated state.
- After committing, fetch the base and this branch's remote. If the remote branch has commits the local branch lacks, integrate them first. Then bring in the fetched base: rebase onto it, or merge it when the repository prefers merge commits, and repeat the validation from [evidence](evidence.md) on the resulting state. If unrelated uncommitted work blocks the rebase, stop and ask; do not stash or discard it.
- Recheck the branch tip and remote relationship immediately before push. When the rebase rewrote published commits, record the remote head you integrated and push with `--force-with-lease=<branch>:<that sha>`; when the lease fails, fetch and integrate again instead of overwriting.
- Push with explicit remote and upstream tracking when needed. Never force-push any other branch.
- If push fails, preserve the local branch and report the provider or permission error. Do not switch to an unapproved fork or remote.
## Create
Before creation, query again for an open PR matching the head repository/branch and base. This closes the race between preparation and publication.
For UI changes, confirm the prepared body embeds or links the required proof before creation. A local path is valid only as an attachment input that the provider rewrites to a hosted URL; supply that attachment with the creation request. With a text-only API, use an already hosted proof URL. If neither route is available, stop before creation, including drafts.
Create through the authenticated provider using explicit repository, base, and head values. If GitHub CLI fails because the GraphQL quota is used up, create through REST, which has a separate quota: `gh api --hostname <host> repos/<owner>/<repo>/pulls -f title=... -f head=... -f base=... -F draft=<true|false> -F body=@<file>`. Supply the selected title, prepared body, requested draft state, and safe evidence attachments. Avoid interactive inference when explicit flags or API fields can carry resolved values.
For fork PRs, identify both head and base repositories. Do not assume the base remote accepts the push. Do not enable maintainer edits, assign reviewers, add labels, or join projects contrary to repository convention or user direction.
## Uncertain writes
Treat a timeout, interrupted command, malformed response, or nonzero result after request transmission as uncertain rather than failed. Query open PRs for the exact head repository/branch and base, then compare head commit and title. Retry only when provider state proves that creation did not occur.
Apply the same rule to attachments or later body edits: read current remote content before retrying so evidence is not duplicated.
## Read back
Read the PR from the provider and verify:
- host, repository, number, and URL;
- open state and requested draft state;
- base branch;
- head repository, branch, and commit;
- title and required body sections;
- hosted attachment references when media was supplied.
- for UI changes, verify the description contains the required screenshot or recording and its URL is accessible to reviewers; unresolved local paths or missing proof leave publication incomplete.
If read-back differs from the intended target, stop and report the mismatch. Do not silently edit an unexpected PR.
Return the verified PR identity, head commit, validation evidence, attachment result or omission reason, and any remaining check or review state. Do not claim merge readiness unless live provider evidence establishes it.
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 |