agentleFS
Sign inStart free
frostneyfrostney/knips/.agents/skills/update-pr/SKILL.md

update-pr

Skill1 starsChanged 54 days agoMITView on GitHub

Commits relevant changes, merges the remote default when needed, pushes the current pull-request branch, and refreshes stale PR metadata. Use when the user runs /update-pr or asks to update a pull request.

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    When the current PR belongs to a native GitHub stack, read ../git-workflow/references/github-stacks.md.

    line 19
  2. Distinctive:

    Stop if on the base branch or no open PR exists.

    line 26
  3. Very specific:

    When an ordinary branch is behind the remote base, merge it into the branch.

    line 28
  4. Distinctive:

    Run the repository's declared PR gate unless it already passed on the unchanged current diff.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 14 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

Update PR

The request authorizes the repository's declared PR gate, relevant commits, a plain push to the current PR branch, and metadata reconciliation. It does not authorize unrelated changes.

When the current PR belongs to a native GitHub stack, read ../git-workflow/references/github-stacks.md.

  1. Inspect repository state, recent commits, the remote default branch, and the current PR, including its mergeable_state: a dirty (unmergeable) PR gets no pull_request workflow runs whatsoever, so missing CI is resolved by merging the base per step 3, never by retriggers.
  2. Stop if on the base branch or no open PR exists; report the required next workflow.
  3. When an ordinary branch is behind the remote base, merge it into the branch. For a verified native stack, capture remote heads and use the guarded gh stack sync or narrower official stack operation; never use raw rebase or force-push commands.
  4. Run the repository's declared PR gate unless it already passed on the unchanged current diff.
  5. Stage only relevant files and commit them with a concise Conventional Commit subject. Never amend and never skip hooks.
  6. Push an ordinary branch normally, setting upstream when needed. Push a verified stack only through the guarded official stack workflow.
  7. Reconcile the PR title and body with the current commits, scope, linked issues, and observed verification. Keep the title a Conventional Commit subject for the whole change; the squash merge makes it the commit subject on the base branch, so widened scope may also change its type. Preserve the project template or existing body structure and omit filler or repeated summaries.
  8. Report the commit, branch, PR URL, native stack position when applicable, metadata changes, rewritten stack branches if any, and observed validation.

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.

Check your setup, free