agentleFS
ashaychangwaniashaychangwani/imprint/.claude/skills/pr/SKILL.md

pr

Skill24 starsChanged 33 days agoMITView on GitHub

Open a pull request with conventional title, structured description, and pre-flight checks.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

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

    Run these in parallel and report results:

    line 20
  2. Distinctive:

    If any fail, show the errors and ask the user whether to proceed or fix first.

    line 27
  3. Distinctive:

    Run these to understand the branch:

    line 31
  4. Very specific:

    Run git remote -v and git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null to check if the branch is pushed.

    line 58
  5. Very specific:

    If not pushed, run git push -u origin <branch>.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

PR Skill

Open a pull request for the current branch with proper conventions.

Step 1 — Pre-flight checks

Run these in parallel and report results:

bun run lint
bun run typecheck
bun test

If any fail, show the errors and ask the user whether to proceed or fix first.

Step 2 — Gather context

Run these to understand the branch:

  • git branch --show-current — current branch name
  • git log main..HEAD --oneline — commits on this branch
  • git diff main..HEAD --stat — files changed

Step 3 — Determine PR title

The PR title must be a conventional commit format: <type>(<scope>): <description>

Pick type and scope the same way as the /commit skill, but based on the overall branch intent (not individual commits).

Step 4 — Write PR description

Use this structure:

## Summary
- Bullet 1: what changed and why
- Bullet 2: key design decisions
- Bullet 3: anything reviewers should pay attention to

## Test plan
- [ ] Tests pass locally
- [ ] Specific scenario tested

Step 5 — Check remote

Run git remote -v and git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null to check if the branch is pushed.

If not pushed, run git push -u origin <branch>.

Step 6 — Create PR

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

Show the PR URL to the user when done.

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.