agentleFS
Sign inStart free
diegopachecodiegopacheco/agent-skills/git-gh-skill/SKILL.md

git-gh-skill

Skill0 starsChanged 3 months agoUnlicenseView on GitHub

When need to use git or gh commands, use this skill to create a git or gh commands. IF user mentiond git or gh, use this skill. Also to commit/pull/merge code to git or gh, use this skill.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    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:

    always use merge strategy, rebase is not allowed, never use rebase.

    line 8
  2. Distinctive:

    Never add Co-Authored-By lines to commits

    line 11
  3. Distinctive:

    Add the name of project: $message - make sure is concise and clear.

    line 12
  4. Very specific:

    Never push. Never run git push (or any variant like --force, --tags, gh repo sync).

    line 15
  5. Distinctive:

    Only commit locally. The user pushes manually.

    line 16
  6. Distinctive:

    Always explain the task (3-5 lines MAX)

    line 19
  7. Distinctive:

    Always put the whole prompt on the PR description (with proper markdown formatting)

    line 20
  8. Distinctive:

    Always run the tests and get the test output on the PR.

    line 21

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

Git Merge

  • always use merge strategy, rebase is not allowed, never use rebase.

Git Commits

  • Never add Co-Authored-By lines to commits
  • Add the name of project: $message - make sure is concise and clear. Ideally 2-3 linex max.

Git Push

  • Never push. Never run git push (or any variant like --force, --tags, gh repo sync).
  • Only commit locally. The user pushes manually.

Github Pull Request(PR) Guidelines

  • Always explain the task (3-5 lines MAX)
  • Always put the whole prompt on the PR description (with proper markdown formatting)
  • Always run the tests and get the test output on the PR. (with proper markdown formatting)

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.

Check your setup, free