agentleFS
alamenaialamenai/terrae/.claude/skills/pr/SKILL.md

pr

Skill245 starsChanged 9 months agoMITView on GitHub

Commit, push, and open a pull request on GitHub

  • Reads credentials
  • Commits and pushes

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. About 0 are common, 14 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    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, push the branch, and open a pull request on GitHub.

    line 9
  2. Distinctive:

    Run git status to see changed files

    line 14
  3. Distinctive:

    Run git diff --staged and git diff to see all changes

    line 15
  4. Distinctive:

    Run git log --oneline -5 to see recent commits

    line 16
  5. Distinctive:

    Never stage sensitive files (.env, credentials, etc.)

    line 20
  6. Very specific:

    Follow conventional commit format: type(scope): description

    line 21
  7. Distinctive:

    Keep commit messages concise (under 72 characters)

    line 22
  8. Very specific:

    If on main, create a new branch: git checkout -b <branch-name>

    line 25
  9. Distinctive:

    If already on a feature branch, use it

    line 27
  10. Very specific:

    Add --label flags to gh pr create based on the PR type and scope.

    line 33
  11. Very specific:

    Run gh label list to check available labels if unsure.

    line 51
  12. Very specific:

    Use gh pr create to open the PR

    line 58
  13. Distinctive:

    Write a clear title (under 70 characters)

    line 59
  14. Distinctive:

    Write a description that follows the structure below based on PR type

    line 60
  15. Distinctive:

    Start with a Type checklist — check the one that applies:

    line 61
  16. Distinctive:

    Run git status to confirm clean state

    line 96
  17. Distinctive:

    Do NOT push to main directly — always use a feature branch

    line 100
  18. Distinctive:

    Do NOT force push unless explicitly requested

    line 101
  19. Distinctive:

    Ask user before proceeding with each step

    line 102

≈ “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

Pull Request Skill

Commit changes, push the branch, and open a pull request on GitHub.

Instructions

  1. Check Current State
    • Run git status to see changed files
    • Run git diff --staged and git diff to see all changes
    • Run git log --oneline -5 to see recent commits
  2. Stage and Commit
    • Stage specific files by name (avoid git add -A or git add .)
    • Never stage sensitive files (.env, credentials, etc.)
    • Follow conventional commit format: type(scope): description
    • Keep commit messages concise (under 72 characters)
  3. Create or Use Branch
    • If on main, create a new branch: git checkout -b <branch-name>
    • Branch name format: type/short-description (e.g., feat/code-comparison, fix/marker-cleanup)
    • If already on a feature branch, use it
  4. Push to Remote
    • Push with upstream tracking: git push -u origin <branch-name>
  5. Assign Labels Add --label flags to gh pr create based on the PR type and scope.

    Type labels — pick based on the commit type:

    Commit typeLabel
    fixbug
    featenhancement
    docsdocumentation
    test(no type label)
    refactor(no type label)
    chore(no type label)

    Component labels — if the scope matches a component label in the repo, add it:

    ScopeLabel
    compassCompass
    interactionInteraction

    Run gh label list to check available labels if unsure. Multiple labels can be combined:

    gh pr create --label "bug" --label "Compass" ...
  6. Open Pull Request

    • Use gh pr create to open the PR
    • Write a clear title (under 70 characters)
    • Write a description that follows the structure below based on PR type
    • Start with a Type checklist — check the one that applies:
    gh pr create --title "type(scope): description" --label "label" --body "$(cat <<'EOF'
    ## Type
    
    - [ ] Feature
    - [ ] Bug fix
    - [ ] Refactor
    - [ ] Test
    - [ ] Docs
    - [ ] Chore
    
    ## Summary
    - bullet points describing what changed and why
    
    ## Bug Details (only for bug fixes)
    **What was the bug?**
    Describe the incorrect behavior.
    
    **Why did it happen?**
    Explain the root cause.
    
    **How was it fixed?**
    Describe the solution.
    
    ## Test Coverage
    If tests were added or updated, link to the file on the branch (permalink):
    - [`src/registry/map/__tests__/component.test.tsx`](https://github.com/alamenai/terrae/blob/<branch-name>/src/registry/map/__tests__/component.test.tsx)
    EOF
    )"
  7. Verify and Report
    • Show the PR URL to the user
    • Run git status to confirm clean state

Important Rules

  • Do NOT push to main directly — always use a feature branch
  • Do NOT force push unless explicitly requested
  • Ask user before proceeding with each step

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.