agentleFS
MarcusJellinghausMarcusJellinghaus/mcp-tools-py/.claude/skills/commit_push/SKILL.md

commit_push

Skill21 starsChanged 3 months agoMITView on GitHub

Format code, review changes, commit, and push to remote

  • Commits and pushes

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

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

    Follow this process to commit and push your changes:

    line 17
  2. Very specific:

    Use mcp__mcp-tools-py__run_format_code to format all code (black + isort).

    line 20
  3. Very specific:

    Use mcp__mcp-workspace__git with command "status" to check working directory state.

    line 23
  4. Very specific:

    Use mcp__mcp-workspace__git with command "diff" to review the changes.

    line 24
  5. Distinctive:

    Create a commit with a clear, conventional commit message:

    line 30
  6. Distinctive:

    Keep summary under 50 characters

    line 33
  7. Distinctive:

    If the branch doesn't exist on remote yet:

    line 41

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

Commit and Push Changes

Follow this process to commit and push your changes:

1. Format Code

Use mcp__mcp-tools-py__run_format_code to format all code (black + isort).

2. Review Changes

Use mcp__mcp-workspace__git with command "status" to check working directory state. Use mcp__mcp-workspace__git with command "diff" to review the changes.

3. Stage Changes

Stage all relevant changes (exclude any files that shouldn't be committed).

4. Commit

Create a commit with a clear, conventional commit message:

  • Use format: type(scope): description
  • Types: feat, fix, docs, style, refactor, test, chore
  • Keep summary under 50 characters
  • No Claude Code footer or attribution in commit message

5. Push

git push

If the branch doesn't exist on remote yet:

git push -u origin HEAD

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.