agentleFS
KUNDURUHIMANEESHREDDYKUNDURUHIMANEESHREDDY/saber/.agents/skills/create-draft-pr/SKILL.md

create-draft-pr

Skill0 starsChanged 55 days agoMITView on GitHub

Create a draft pull request for the current session. Use when the user wants to open a draft PR with the session's changes.

4 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Use the GitHub MCP server to create a draft pull request if available, otherwise use gh CLI.

    line 9
  2. Distinctive:

    Run the compile and hygiene tasks (fixing any errors)

    line 11
  3. Very specific:

    If there are any uncommitted changes, use the /commit skill to commit them

    line 12
  4. Distinctive:

    Write a clear, concise PR title with a short area prefix (e.g.

    line 14
  5. Distinctive:

    Write a description covering what changed, why, and anything reviewers should know

    line 15
  6. Distinctive:

    Create the draft pull request

    line 16

“Common” is measured: kept by at least 6 in 10 of the 4 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
<!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->

Create Draft Pull Request

Use the GitHub MCP server to create a draft pull request if available, otherwise use gh CLI.

  1. Run the compile and hygiene tasks (fixing any errors)
  2. If there are any uncommitted changes, use the /commit skill to commit them
  3. Review all changes in the current session
  4. Write a clear, concise PR title with a short area prefix (e.g. "sessions: …", "editor: …")
  5. Write a description covering what changed, why, and anything reviewers should know
  6. Create the draft pull request

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.