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.

syncing.md

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

syncing.md — bring the PR up to date

Entry: an open PR has fallen behind its base or has conflicts. Saves nothing. Syncing preserves the caller's completion mode and defaults to snapshot mode when entered directly; control continues at checks.md.

  1. git fetch origin, then rebase the branch onto the base — or merge, if the PR's existing history style is merge-based; follow what the PR already does.
  2. Resolve conflicts by understanding both sides: read the conflicting hunks' history (git log -p on each side) before choosing. A mechanical "take ours" is how freshly merged work gets silently reverted.
  3. Reassess verification evidence. Apply the spine's final-tree rule to the resulting change. Inspect conflict resolutions, relevant dependency changes, and base commits touching the change's behavior or test surface when deciding which gates were invalidated; use the full bar only when the base moved substantially enough to invalidate it. Changed commit ancestry alone does not force a rerun.
  4. If step 3 causes a fix, commit it and repeat step 3 against the new head. Push only after evidence covers the final tree and git status --porcelain is empty (the spine's point-of-action rule). Use --force-with-lease after a rebase, never plain --force.

Red flags: "a rebase happened, so rerun everything" ignores valid evidence; "no conflicts, so every old result still applies" ignores relevant behavior or dependency changes. Reassessing evidence is unconditional; rerunning commands is not.

Next

Read and follow checks.md in the selected completion mode.

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