agentleFS
Sign inStart free
rstackjsrstackjs/agent-skills/.agents/skills/pr-creator/SKILL.md

pr-creator

Skill97 starsChanged 3 months agoMITView on GitHub

Create a pull request using repository branch rules, title conventions, templates, and concise English descriptions.

  • Commits and pushes

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    If it is the default branch, create and switch to a new branch before doing anything else.

    line 13
  2. Very specific:

    Use a descriptive branch name, preferably feat-<topic> or fix-<topic>.

    line 14
  3. Distinctive:

    Do not revert unrelated user changes.

    line 17
  4. Distinctive:

    Before creating the PR, ensure the intended changes are committed and never commit directly on the default branch.

    line 18
  5. Distinctive:

    Read the repository's PR template when available and follow its current headings and guidance.

    line 20
  6. Distinctive:

    Write the PR body in concise, clear English.

    line 31
  7. Distinctive:

    Keep typical descriptions to a few short sentences.

    line 34
  8. Very specific:

    When running in Codex, use the Codex GitHub connector/plugin for GitHub operations.

    line 43
  9. Very specific:

    Use gh pr create only as a fallback when the connector is unavailable.

    line 44
  10. Distinctive:

    Do not modify code while following this skill.

    line 48

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

Pull request creator

Steps

  1. Confirm the current branch with git branch --show-current. If it is the default branch, create and switch to a new branch before doing anything else. Use a descriptive branch name, preferably feat-<topic> or fix-<topic>.
  2. Review local changes with git status --short. Do not revert unrelated user changes. Before creating the PR, ensure the intended changes are committed and never commit directly on the default branch.
  3. Read the repository's PR template when available and follow its current headings and guidance.
  4. Draft the PR title in the repository's standard format. If the repository uses Conventional Commits, common patterns include:
    • feat(core): add ...
    • fix(types): ...
    • docs: ...
    • refactor(types): ...
    • chore(ci): ... for CI workflow, check, or release automation changes
    • chore(deps): ...
    • release: v1.2.0
  5. Write the PR body in concise, clear English.
    • Explain the problem or motivation and why it matters, then describe the approach and resulting behavior.
    • Include API, compatibility, or migration details when they help reviewers assess the change.
    • Keep typical descriptions to a few short sentences. Focus on the key changes rather than a file-by-file summary.
    • Include tests, documentation, and validation required by repository guidelines or the template. Otherwise, mention them only when central to the change or relevant to review risk.
  6. Include relevant issue, discussion, or design links alongside the context they support, following the template's guidance. For dependency upgrades, link to the target version's release notes or tag when available.
  7. Push the branch only after re-checking the branch name. Never push the default branch directly.
  8. Create the PR. When running in Codex, use the Codex GitHub connector/plugin for GitHub operations. Use gh pr create only as a fallback when the connector is unavailable.

Constraints

  • Do not modify code while following this skill.

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