agentleFS
roborracleroborracle/agent-workflow-kit/skills/pr-workflow/SKILL.md

pr-workflow

Skill0 starsChanged 3 months agoMITView on GitHub

Create a pull request with auto-generated title, body, and linked issues from commit history (create PR, open pull request, submit PR).

  • Commits and pushes

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use workflow and code-review.

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.
  • VercelSkill

    workflow

    Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", or step-based orchestration.

    Also in 4 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 4

    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:

    If there are uncommitted changes, warn the user

    line 40
  2. Distinctive:

    If there are no commits vs main, abort with a message

    line 41
  3. Very specific:

    Verify the branch is pushed to remote: git push -u origin $(git branch --show-current)

    line 42
  4. Distinctive:

    Always link to issues found in commit messages

    line 78
  5. Distinctive:

    Keep summary concise — the diff tells the full story

    line 79

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

Pre-fetched Context

Current Branch

!git branch --show-current 2>/dev/null

Commits on This Branch (vs main)

!git log main..HEAD --oneline 2>/dev/null || git log origin/main..HEAD --oneline 2>/dev/null || echo "Cannot determine commits vs main"

Changed Files

!git diff main..HEAD --name-only 2>/dev/null || echo "Cannot determine changed files"

Diff Stats

!git diff main..HEAD --stat 2>/dev/null || echo "Cannot determine diff stats"

Open Issues Referenced in Commits

!git log main..HEAD --pretty=format:"%s" 2>/dev/null | grep -oE "#[0-9]+" | sort -u || echo "No issue references found"

Uncommitted Changes

!git status --porcelain 2>/dev/null


Your Task

Using the pre-fetched data above:

1. Pre-flight Checks

  • If there are uncommitted changes, warn the user
  • If there are no commits vs main, abort with a message
  • Verify the branch is pushed to remote: git push -u origin $(git branch --show-current)

2. Generate PR Content

From the commit history, generate:

Title: Under 70 characters, summarizing the change. Use the dominant commit type (feat/fix/refactor).

Body:

## Summary
[2-3 bullet points describing what changed and why, derived from commit messages]

## Changes
[List of significant files changed with brief explanation]

## Issues
[List of Closes #N / Fixes #N from commit messages]

## Testing
- [ ] All tests passing
- [ ] Type checker passes
- [ ] Linter passes
- [ ] Manual testing completed

3. Create the PR

gh pr create --title "title" --body "$(cat <<'EOF'
body content
EOF
)"

4. Return the PR URL

Rules

  • Always link to issues found in commit messages
  • Keep summary concise — the diff tells the full story
  • Base branch defaults to main unless $ARGUMENTS specifies otherwise

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.