agentleFS
Sign inStart free
zekhoizekhoi/claude/.agents/skills/kit-pull-request/SKILL.md

kit-pull-request

Skill0 starsChanged 20 days agoMITView on GitHub

Prepare and open pull requests (GitHub) or merge requests (GitLab) with an accurate title, description, and test plan drawn from the branch's actual commits and diff. Use when the user asks to open, create, draft, or update a PR or MR, or to write its description. Do not use for reviewing someone else's PR or MR, committing, or merging.

  • Commits and pushes

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Read git log <base>..HEAD and git diff <base>...HEAD.

    line 13
  2. Distinctive:

    Check for uncommitted changes and for commits not yet pushed.

    line 14
  3. Very specific:

    Use the repository's PR or MR template if one exists (.github/pull_request_template.md, .github/PULL_REQUEST_TEMPLATE/, …

    line 18
  4. Distinctive:

    Keep it proportional to the change.

    line 29
  5. Distinctive:

    If the CLI is missing or unauthenticated, or there is no remote, do not work around it.

    line 35
  6. Distinctive:

    Use: "Open a PR for this branch." "Write the MR description." "Update the PR description with the new changes."

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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

Pull or merge request

Opening a PR or MR is visible to others. Do it only when the user asked to open one; otherwise produce the title and description for them. Never merge, approve, close, or force-push unless the user explicitly asks.

1. Understand the branch

  • Identify the current branch and its base: the user's stated target, otherwise the repository's default branch (git remote show origin, gh repo view --json defaultBranchRef, or glab repo view).
  • Read git log <base>..HEAD and git diff <base>...HEAD. Describe what the branch actually changes, not only the latest commit.
  • Check for uncommitted changes and for commits not yet pushed. Ask before committing or pushing anything on the user's behalf.

2. Follow project conventions

  • Use the repository's PR or MR template if one exists (.github/pull_request_template.md, .github/PULL_REQUEST_TEMPLATE/, .gitlab/merge_request_templates/).
  • Match the title style of recent merged PRs or MRs and the commit convention.
  • Reference related issues using the syntax the platform understands (Fixes #123, Closes group/project#123).

3. Write the description

  • Summary: what changed and why, in a few sentences.
  • Changes: the notable changes, grouped logically. Call out breaking changes, migrations, configuration changes, and new dependencies.
  • Testing: what was run and the result. If something was not tested, say so. Do not claim checks passed unless you ran them or saw their results.
  • Notes for reviewers: risky areas, follow-ups, and anything intentionally out of scope.

Keep it proportional to the change. Do not pad small changes.

4. Open or update it

  • GitHub: gh pr create --base <base> --title ... --body ... (add --draft when the work is incomplete); update with gh pr edit.
  • GitLab: glab mr create --target-branch <base> --title ... --description ... (--draft when incomplete); update with glab mr update.
  • If the CLI is missing or unauthenticated, or there is no remote, do not work around it. Give the user the title and description and the command to run.

5. Report

Give the PR or MR link, its base branch, and any checks or reviews it is waiting on.

Examples

  • Use: "Open a PR for this branch." "Write the MR description." "Update the PR description with the new changes."
  • Skip: "Review PR #42." (use kit-code-review) "Merge it." (requires an explicit instruction) "Commit this."

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