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/evidence.md
View on GitHub# Validation and evidence
Collect evidence before committing or publishing. Evidence proves the current intended state, not an earlier revision.
## Validation
- Discover required commands from repository instructions, CI configuration, package scripts, build files, and changed-surface documentation.
- Inspect commands before running them. Do not use fixers, snapshot updates, code generation, deployments, or other state-changing checks unless they are ordinary authorized implementation steps.
- Run repository-required pre-PR checks plus the smallest focused check that proves the changed behavior.
- After checks, inspect the worktree again. Classify generated changes and exclude or stop on anything unexpected.
- Record the exact command, exit status, relevant outcome, and tested state. A passing unrelated suite is not evidence for the changed behavior.
- Stop on a required or relevant failure. Report infrastructure or missing-tool failures distinctly from product failures.
## Evidence selection
Prefer the cheapest artifact that lets a reviewer verify success:
1. Focused test or assertion output.
2. Required validation and static checks.
3. Before/after metrics or structured output.
4. Image or video for visual, rendered, interaction, or otherwise materially clearer results.
For UI changes, the PR description must include UI proof: at least one screenshot or recording of the actual changed interface, embedded or linked with a durable URL reviewers can open. Capture the state being published and explain the screen, state, viewport, and reproduction steps. Include before/after views when they help demonstrate the change. Local paths, placeholders, test logs, and promises to attach proof later do not satisfy this gate.
Stop before PR creation, including drafts, if UI proof cannot be captured safely or made accessible. Report the missing environment, access, or attachment capability. For non-UI changes, media remains optional; use it only when it communicates proof better than text. Never create a decorative terminal screenshot or other quota-filling artifact.
For changed behavior, reproduce the same scenario against the baseline and the
proposed state when safely possible. Match the application instance, project,
provider, model, permission mode, and creation path when they affect the outcome.
Record the before and after results and revisions. A repaired existing object
does not prove a fresh-object creation path. If the baseline cannot be exercised,
say why and distinguish inspected behavior from runtime evidence. Documentation
changes may use a concrete before/after example rather than a fabricated failure.
## Attachment safety
Before upload, inspect the actual media at full resolution and check for credentials, tokens, customer or personal data, internal hostnames, private paths, usernames, unrelated applications, notifications, browser tabs, and unintended screen regions. Use meaningful alt text that states what the evidence shows.
For GitHub CLI:
- detect `--attach` from the installed command's help instead of assuming a version;
- supported formats are PNG, JPEG, GIF, WebP, SVG, MP4, MOV, and WebM, subject to live provider limits;
- quote `'<path>#<alt text>'` so the shell does not treat `#` as a comment;
- repeat `--attach` for multiple files;
- reference the local path in body Markdown when placement matters; `gh` rewrites it to the hosted URL;
- treat GitHub Enterprise Server and insufficient write permission as potentially unsupported even when local help lists the flag.
If attachment support is unavailable for a UI change, use an existing safe hosted artifact or another repository-approved attachment route; if neither is available, stop before creation. For non-UI changes only, continue with textual evidence and report why media was omitted. An attachment failure does not justify retrying PR creation blindly.
The evidence gate passes when required checks succeed, every PR claim maps to captured evidence from the state being published, and UI changes have safe proof ready for inclusion in the description.
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 |