Index of every page on this site: llms.txt
All skills
jetbrains avatar

/shipping-a-pr

@e85862d
by jetbrainsjetbrains/thinkrail8.4k stars
532
Run it yourself

Use when finished work needs to ship as a pull request, or when creating, syncing, updating metadata, checking status, monitoring CI, or addressing review comments on a PR. Not for reviewing a PR you are not shipping.

Use this Skill: https://skilld.dev/gh/jetbrains/thinkrail/shipping-a-pr

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

review-comments.md

≈423 tokens on demand. Your agent reads this file only when SKILL.md points to it.

review-comments.md — address comments, never blindly

Entry: an open PR has review comments to address. Saves nothing. Snapshot mode is the default whether or not an accepted fix is pushed. Preserve wait mode only when selected by the spine's explicit remote-completion rule.

  1. Whole-PR read first. Fetch every comment thread and the full diff (gh pr view <n> --comments, gh api repos/<owner>/<repo>/pulls/<n>/comments --paginate), then re-read the PR's changes end to end. Each comment is judged against the whole change, not just its quoted lines.
  2. Verdict per comment, before touching code: apply (it's right), push back (it's wrong or misreads the design — say why, citing the spec or design), or clarify (genuinely ambiguous — ask the reviewer or the user). Batch the verdicts; surface them to the user whenever any verdict is push-back.
  3. Apply the accepted ones as proper changes, then apply the spine's final-tree verification rule. Commit everything and repeat that rule if verification causes another fix; push only when evidence covers the clean final tree. Reply to every thread only after the push lands: what changed and where (naming the commit), or the push-back rationale. Resolve only threads actually addressed.

Red flags:

  • Patching exactly the quoted line without reading the surrounding design — "do not fix them blindly" is this doc's founding requirement.
  • Replying "done" without a pushed commit that shows it.
  • Silently skipping a comment — every thread gets an answer.

Next

Read and follow checks.md in the selected completion mode, including snapshot mode after an ordinary pushed fix.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning22d3 checks · Risk SAFE
  • Gen Agent Trust Hub22d

    The skill provides a structured workflow for managing GitHub Pull Requests, including creation, syncing, and review management. It is functionally appropriate but possesses a vulnerability surface for indirect prompt injection as it processes external content like PR comments and repository templates without explicit sanitization or boundary markers.

  • Socket22d

    No alerts

  • Snyk22d

    Risk: MEDIUM · 1 issue

Signed by skilld at e85862d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated last week

README badge

README badge for jetbrains/thinkrail/shipping-a-pr