agentleFS
netanelavrnetanelavr/dotcursor/skills/kit-create-pr/SKILL.md

kit-create-pr

Skill6 starsChanged 27 days agoMITView on GitHub

Commit changes and create a pull request with proper formatting. Use when ready to publish work for review.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 9 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Commit changes and create a pull request with proper formatting.

    line 9
  2. Distinctive:

    Read the current branch:

    line 15
  3. Very specific:

    If the branch or the user supplies a tracker id (Jira, Linear, GitHub issue, and similar), prefix commit and PR titles with it, for example …

    line 19
  4. Distinctive:

    Do not: run git add -A (or stage everything) unless they explicitly approve that full set.

    line 31
  5. Distinctive:

    Default: stage only the paths they named, or ask which paths to include.

    line 32
  6. Distinctive:

    Ask: "What did users experience that was wrong?"

    line 53
  7. Distinctive:

    Use descriptive lowercase names with hyphens

    line 90
  8. Very specific:

    Strip: if the diff is fatter than the outcome, kit-strip-diff before review.

    line 95
  9. Very specific:

    Review: prefer kit-review author on the branch diff before publish.

    line 96
  10. Distinctive:

    Diff: no secrets, no probe/TEMP validation junk, no unrelated drive-bys.

    line 98
  11. Distinctive:

    History: do not force-push to the default branch.

    line 99
  12. Distinctive:

    After completion, provide user with (DO NOT wrap in code block - URLs must be clickable):

    line 133

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

Create PR

Commit changes and create a pull request with proper formatting.

Flow

1. Optional tracker id

Read the current branch:

git rev-parse --abbrev-ref HEAD

If the branch or the user supplies a tracker id (Jira, Linear, GitHub issue, and similar), prefix commit and PR titles with it, for example [ABC-123]. If there is none, omit the prefix. Do not invent an id.

2. Commit Changes

A. Check git status:

git status

B. Stage changes:

  1. Show git status / the file list to the user.
  2. Do not run git add -A (or stage everything) unless they explicitly approve that full set.
  3. Default: stage only the paths they named, or ask which paths to include.
git add path/to/file [...]

C. Commit:

git commit -m "Fix: <problem users experience>"
# or, if a tracker id exists:
git commit -m "[ABC-123] Fix: <problem users experience>"

Commit message format:

  • Bug fix: Fix: <problem users experience>
  • Feature: Feature: <what users can now do>
  • Improvement: Improve: <what's better for users>
  • Refactor: Refactor: <description>
  • With tracker: [ABC-123] Fix: <problem users experience>

Important:

  • Describe the PROBLEM, not your solution
  • Ask: "What did users experience that was wrong?"

3. Create Pull Request

A. Push the branch:

git push -u origin HEAD

B. Create PR using gh CLI:

gh pr create \
  --title "Fix: <problem users experience>" \
  --body "## Problem
<What users experienced - why this matters to them>

## Solution
<Brief explanation of how it's fixed>"

Best Practices

Commit Message

  • Format: Type: Description (optional [TRACKER-ID] prefix)
  • Types: Fix, Feature, Improve, Refactor
  • Description: Describe the problem being fixed, not the code change
  • Length: One line, < 72 chars if possible
  • Tense: Imperative mood (Fix, Add, Update - not Fixed, Added, Updated)
  • Bad: "Add null check to user handler" (what you did)
  • Good: "Users see crash when opening empty profile" (what users experienced)

PR Description

  • Problem: What the user experienced (lead with this, make it clear why it matters)
  • Solution: Brief explanation of how it's fixed (keep technical details minimal)
  • Skip "Root Cause" and "Changes" sections - focus on user impact

Branch Naming

  • Use descriptive lowercase names with hyphens
  • Examples: fix-login-redirect, feature-chat-export, improve-loading-speed

Hygiene (before publish)

  • Strip: if the diff is fatter than the outcome, kit-strip-diff before review.
  • Review: prefer kit-review author on the branch diff before publish.
  • Branch: descriptive lowercase with hyphens (fix-…, feature-…). Prefer syncing with default branch before open if the branch is stale (git fetch + rebase/merge per repo norm).
  • Diff: no secrets, no probe/TEMP validation junk, no unrelated drive-bys.
  • History: do not force-push to the default branch. Force-push to your feature branch only if the user explicitly asks.
  • Remote: push with -u on first publish; confirm gh pr view / URL after create.

Troubleshooting

Finding Current Branch PR

gh pr view --json number,url,title

Example Complete Flow

1. Branch: fix-new-chat-reload (no tracker id)

2. Commit:
   git commit -m "Fix: New Chat button returns to previous chat after reload"
   
3. Push:
   git push -u origin fix-new-chat-reload

4. Create PR:
   gh pr create \
     --title "Fix: New Chat button returns to previous chat after reload" \
     --body "## Problem
   Users click New Chat expecting a fresh conversation, but after page reload they see the previous chat instead.
   
   ## Solution
   Clear chat state properly when starting a new conversation."
   
   → Result: PR #1780

Output Format

After completion, provide user with (DO NOT wrap in code block - URLs must be clickable):

✅ Commit: <Type>: <Description>

✅ PR: #NUMBER - <Title>

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.