agentleFS
arklexaiarklexai/arksim/.claude/skills/draft-pr/SKILL.md

draft-pr

Skill234 starsChanged 8 months agoApache-2.0View on GitHub

Generate a PR title and description from your changes

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use interview and frontend-design.

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

    interview

    Interview me about a plan to flesh out requirements before implementation. Asks non-obvious questions one at a time until all ambiguities are resolved.

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 3

    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 multiple areas changed equally, omit scope

    line 24
  2. Distinctive:

    Use imperative mood, lowercase after colon

    line 29
  3. Very specific:

    Read .github/pull_request_template.md and fill in each section with real content from the commits and diff.

    line 33
  4. Distinctive:

    Ensure at least 20 characters of real content (excluding template boilerplate)

    line 36

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

Draft PR

Analyze commits and diff to produce a ready-to-use PR title and description.

Steps

  1. Analyze commits and diff
    git log --oneline main..HEAD
    git diff --stat main..HEAD
    git diff main..HEAD
  2. Determine type and scope
    • Infer type from changes (feat, fix, docs, chore, etc.)
    • Infer scope from primary directory affected
    • If multiple areas changed equally, omit scope
  3. Validate title
    • Must match: ^(feat|fix|docs|chore|ci|build|refactor|test|perf|style|revert)(\([a-z][a-z0-9_-]*\))?!?: .+$
    • Max 72 characters
    • Use imperative mood, lowercase after colon
  4. Read and fill the PR template

    Read .github/pull_request_template.md and fill in each section with real content from the commits and diff. Strip all HTML comments and placeholder text.

  5. Validate description
    • Ensure at least 20 characters of real content (excluding template boilerplate)

Output

Print the title and filled PR template body in raw markdown format, ready to copy:

Title: <type>(<scope>): <description>

<filled-out PR template in raw markdown>

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.