agentleFS
Sign inStart free
otsalomaotsaloma/agent-setup/skills/github-pr/SKILL.md

github-pr

Skill0 starsChanged 44 days agoMITView on GitHub

Prepare a GitHub pull request for the current work —

  • Commits and pushes

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use zeroclaw, github-issue and 2 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.
  • openagenSkill

    zeroclaw

    Help users operate and interact with their ZeroClaw agent instance — through both the CLI (`zeroclaw` commands) and the REST/WebSocket gateway API. Use this skill whenever the user wants to: send messages to ZeroClaw, manage memory or cron jobs, check system status, configure channels or providers, hit the gateway API, troubleshoot their ZeroClaw setup, build from source, or do anything involving the `zeroclaw` binary or its HTTP endpoints. Trigger this even if the user just says things like 'check my agent status', 'schedule a reminder', 'store this in memory', 'list my cron jobs', 'send a message to my bot', 'set up Telegram', 'build zeroclaw', or 'my bot is broken' — these are all ZeroClaw operations.

    Also in 3 projects that use this

  • devstefanchoSkill

    github-issue

    Unified GitHub issue workflow via the gh CLI — fetch an issue (body, labels, comments, image/video attachments) into the session, create a new issue from a template, or update an existing one (body, labels, state, comments). Handles the 404 that plain curl/WebFetch hits on GitHub attachment URLs by downloading with an auth token, and extracts viewable frames from video attachments. Use whenever the user mentions GitHub issues — 이슈 가져와, 이슈 조회, 이슈 등록, 이슈 생성, 이슈 만들어줘, 이슈 업데이트, 이슈 수정, 이슈 코멘트, 이슈 작업, fetch issue N, work on issue N, create an issue, update issue N, file a bug, /github-issue.

    Also in 6 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 8 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 5

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

    If currently on the master or main branch, look at the uncommitted changes and suggest a suitable branch name based on those.

    line 12
  2. Distinctive:

    Check if there are uncommitted changes.

    line 16
  3. Very specific:

    Check if there are unpushed changes.

    line 20
  4. Distinctive:

    Stop if there's nothing pushed to make a PR from.

    line 24
  5. Distinctive:

    If there's only a single commit of changes in the branch, use that commit's title and message as the PR title and description, dropping any …

    line 33
  6. Distinctive:

    If there's more than one commit, look at the commits at a high-level: focus on why, what has been the intent and principles of the solution.

    line 37
  7. Very specific:

    Write the description as unwrapped paragraphs, using proper Markdown formatting for inline code etc.

    line 43

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

Prerequisites:

  1. If currently on the master or main branch, look at the uncommitted changes and suggest a suitable branch name based on those. If approved, create the branch and switch to it.
  2. Check if there are uncommitted changes. If yes, suggest to commit those as per any user- and repository-level commit rules in instructions you have read.
  3. Check if there are unpushed changes. If yes, push those changes without asking. You can do this only for feature branches (not master or main) and only changes you can push without --force.

Stop if there's nothing pushed to make a PR from.

Then use gh pr create --web --title ... --body-file - to prefill a GitHub pull request and open it in a web browser for me. Do not submit the PR, I need to review and submit it myself. With --body-file - use a quoted heredoc (<<'EOF') so that you can use proper Markdown such as backticks without breaking the shell command. If a PR already exists for the branch, just open it with gh pr view --web.

If there's only a single commit of changes in the branch, use that commit's title and message as the PR title and description, dropping any Co-Authored-By line.

If there's more than one commit, look at the commits at a high-level: focus on why, what has been the intent and principles of the solution. Based on that, figure out a suitable PR title and description. Description should be one short paragraph. Do not include technical details like lists of symbols changed.

Write the description as unwrapped paragraphs, using proper Markdown formatting for inline code etc. If fixing or continuing something related to a previous PR, reference that PR in the description by its number (#123). If the work resolves an issue from a tracker, end the description with Closes followed by the issue reference, e.g. Closes #123 or Closes ENG-123. Do not include any attribution line of your own.

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