agentleFS
tariknztariknz/irdashies/.claude/skills/publish-pr/SKILL.md

publish-pr

Skill272 starsChanged 16 days agoMITView on GitHub

Publish GitHub pull requests for this repository. Use this skill whenever the user asks to create, open, raise, or publish a PR. Follow the repository's pull request template exactly, default to a published/ready-for-review PR unless the user explicitly requests a draft, and write a conventional-commit-style title that describes the user-visible problem solved or outcome achieved. Continue with babysit-pr when monitoring or review-comment handling is requested.

  • Commits and pushes

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 10 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read AGENTS.md, .github/pull_request_template.md, and relevant contribution guidance.

    line 12
  2. Distinctive:

    Create or use a correctly named feature branch, commit the intended changes with the repository's commit convention, and push the branch …

    line 15
  3. Distinctive:

    Check whether the current branch already has an open or draft PR.

    line 16
  4. Distinctive:

    Verify the PR has the requested publication state and required screenshot attachments.

    line 20
  5. Distinctive:

    When the user also requests monitoring, babysitting, or handling review comments, continue with babysit-pr.

    line 21
  6. Distinctive:

    Use the conventional prefix and casing style found in recent PR history:

    line 25
  7. Distinctive:

    Keep the title concise, concrete, and understandable without reading the diff.

    line 47
  8. Distinctive:

    Do not check a checklist item based on intention or inference.

    line 54
  9. Distinctive:

    Do not claim iRacing or other live-environment testing unless it was actually performed.

    line 55
  10. Very specific:

    Keep review screenshots and recordings outside the repository worktree, such as in a temporary directory.

    line 61
  11. Distinctive:

    Check the CLI that will actually perform the upload:

    line 63
  12. Distinctive:

    If the installed CLI needs upgrading on Windows and that upgrade is authorized, use:

    line 70
  13. Very specific:

    Use !Screenshot for an image and !

    line 93

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Publish a Pull Request

Publish the current work as a GitHub pull request, ready for review by default.

Workflow

  1. Read AGENTS.md, .github/pull_request_template.md, and relevant contribution guidance.
  2. Inspect the worktree, current branch, diff, commits, and remote. Never commit directly to main.
  3. Determine the intentional PR scope. Preserve unrelated user changes. Run checks appropriate to the changed files and report any checks that cannot be run.
  4. Create or use a correctly named feature branch, commit the intended changes with the repository's commit convention, and push the branch when needed.
  5. Check whether the current branch already has an open or draft PR. Reuse and update it instead of creating a duplicate.
  6. Derive the PR title from recent PR history and the rules below.
  7. Copy .github/pull_request_template.md verbatim for the PR body. Preserve every heading, HTML comment, checklist entry, and their order. Fill in applicable placeholders and check only items actually completed. Every visual change requires actual screenshot attachments as described below. Only changes with no visual impact may mark screenshots as not applicable.
  8. Update the existing PR or create a new one as published and ready for review unless the user explicitly asks for a draft or required screenshot uploads remain blocked. Treat silence about publication state as a request for a published PR once all requirements are satisfied. If an existing PR is a draft and the user requests publication, mark it ready for review only after required screenshots are attached.
  9. Verify the PR has the requested publication state and required screenshot attachments. If the user did not request a draft and tooling unexpectedly leaves one, mark it ready for review and verify again only when its screenshot requirements are satisfied.
  10. When the user also requests monitoring, babysitting, or handling review comments, continue with babysit-pr. Otherwise return the PR's title and URL after publication verification. Publishing alone does not start an ongoing watch or authorize merging.

Title Rules

Use the conventional prefix and casing style found in recent PR history:

<type>: <problem solved or outcome achieved>

Choose the type that matches the work, such as feat, fix, perf, refactor, docs, test, build, ci, or chore.

Describe the problem that is now solved or the capability the user now has. Do not merely name the implementation action, internal symbol, file, bridge, or refactor.

Good:

fix: site missing session bridge causing it to not load

Avoid:

fix: initialize browser session bridge

Keep the title concise, concrete, and understandable without reading the diff. Prefer the repository's established wording when history provides a close precedent, but apply the problem/outcome rule even if an older title was implementation-focused.

PR Body Rules

  • Copy the current repository template verbatim rather than recreating it from memory. Preserve all headings, HTML comments, checklist entries, and their order.
  • Explain the problem, its effect, and how the PR resolves it in the Description.
  • Include exact validation performed and distinguish automated, Storybook, manual, and real-environment testing.
  • Do not check a checklist item based on intention or inference.
  • Do not claim iRacing or other live-environment testing unless it was actually performed.
  • Preserve Before and After screenshot headings.

Review Images and Videos

  • Every visual change must be shown to the user with a screenshot in the final response and have actual screenshots uploaded as GitHub attachments in the PR body. Include Before / After images for changes to existing UI, and at least an After image for new UI. Prose descriptions, Storybook links, and local image paths are not substitutes.
  • Keep review screenshots and recordings outside the repository worktree, such as in a temporary directory. Do not commit them to docs/assets/pr-reviews/ or any other repository path. This does not prevent adding product assets that the user explicitly requested as part of the implementation.
  • Before uploading, check the selected subcommand's --help for --attach (for example, gh pr comment --help). If the installed CLI lacks it, check the current official release and use an updated CLI before declaring upload unavailable. A checksum-verified portable release outside the worktree can use existing authentication without changing the installed CLI. Do not run the examples below unless the selected command advertises the flag.
  • Check the CLI that will actually perform the upload:

    gh --version
    gh pr edit --help

    If the installed CLI needs upgrading on Windows and that upgrade is authorized, use:

    winget upgrade --id GitHub.cli --exact --silent --disable-interactivity

    Windows may request administrator approval. Leave that prompt for the user; do not automate it or report the upgrade complete before it finishes. Re-run gh --version and check the attachment flag afterward. If using a portable release instead, run these checks against that executable's full path.

  • When supported, upload directly with gh pr create, gh pr edit, or gh pr comment and --attach. If the flag is absent, try an authenticated GitHub browser upload instead. If uploads remain blocked, keep the visual PR in draft, report the exact blocker, and continue recovery where possible. Do not claim publication is complete until screenshots are attached; do not commit review assets as a workaround.
  • For a comment attachment when --attach is supported:

    gh pr comment <PR-NUMBER> --body 'Review screenshot' \
      --attach '/path/to/image.png#Screenshot of bug fix'
  • To place media under the template's Before/After headings, write the body to a temporary file with local Markdown references, then pass that file and the same media paths to gh pr create or gh pr edit:

    gh pr edit <PR-NUMBER> --body-file /tmp/pr-body.md \
      --attach /tmp/screenshot.png --attach /tmp/replay.mp4

    Use ![Screenshot](/tmp/screenshot.png) for an image and ![](/tmp/replay.mp4) in its own paragraph for a video player. gh replaces the local references with uploaded attachment URLs. Repeat --attach for additional files.

  • Read back the PR body and verify that the uploaded attachments render and no local paths or repository-hosted review media links remain. A normal GET of each image URL can also verify delivery; do not treat a failed HEAD request alone as proof the attachment is broken. If an upload partially fails, inspect the saved body before retrying to avoid duplicates.

Publication Guardrail

Published means ready for review, not merely pushed to a remote. Visual PRs also require verified screenshot attachments before they can be marked ready for review. Unless the user explicitly requests a draft or screenshot uploads remain blocked, confirm the PR's draft flag is false before completing the task. When the user explicitly requests a draft or required screenshot uploads remain blocked, create or retain and verify a draft PR instead, and explain any blocker. Never create a duplicate PR when the branch already has one.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.