agentleFS
cogine-aicogine-ai/cogine-dev-skillset/skills/file-pr/SKILL.md

file-pr

Skill3 starsChanged 5 months agoApache-2.0View on GitHub

File or update a GitHub PR for a prepared branch when requested, including as part of takeover.

  • Commits and pushes

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use docs-loop, full-loop and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GeiserXSkill

    docs-loop

    Use when the user asks to audit docs, check documentation for stale claims, or verify docs against the code.

    Also in 3 projects that use this

  • GeiserXSkill

    full-loop

    Drive a repository to done with sergio-loop, then keep improving it with refine-loop at a descending theta. Use only when the user explicitly invokes full-loop.

    Also in 3 projects that use this

  • +7 more from GeiserX

The file

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 24 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
  1. Distinctive:

    Use when publishing an already prepared change is part of the user's request.

    line 8
  2. Distinctive:

    If the same head has an open PR against a different base, confirm which PR the user wants before opening another.

    line 13
  3. Distinctive:

    Follow the repository's title and template conventions.

    line 15
  4. Very specific:

    Create or update the PR with gh.

    line 19

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

File PR

Use when publishing an already prepared change is part of the user's request.

  1. Confirm the intended head repository, branch, and base, and inspect the branch diff. Push the prepared branch if needed and authorized. Find any open PR for that head and base and update it instead of creating a duplicate. If the same head has an open PR against a different base, confirm which PR the user wants before opening another.
  2. Follow the repository's title and template conventions. Start the body with the problem or previous behavior, then describe the change and summarize verification. Follow the user's request and repository conventions for draft status and model attribution. Use only verified model or host names.
  3. Create or update the PR with gh. If gh pr create hits a GraphQL rate limit, check for the matching PR via REST before retrying. If it is absent, use gh api --method POST repos/<owner>/<repo>/pulls with the resolved head and base, title, draft status, and -F body=@<file>.
  4. Return the PR URL to the caller.

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.