agentleFS
Sign inStart free
pauloribeiro16pauloribeiro16/my-skills/commit-workflow/SKILL.md

commit-workflow

Skill1 starsChanged 6 months agoMITView on GitHub

Git workflow automation for committing, pushing, and creating pull requests. Trigger phrases: commit changes, push to remote, create pull request, clean up branches, git workflow

  • Reads credentials
  • Commits and pushes

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When to use: After merging and deleting remote branches.

    line 83
  2. Distinctive:

    Ensure all changes are complete and tested

    line 93
  3. Distinctive:

    Use when minimizing context switching

    line 95
  4. Distinctive:

    Run periodically to keep branch list clean

    line 98

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

Commit Workflow

Streamline git operations with commands for committing, pushing, and cleaning up branches. Based on Anthropic's commit-commands plugin.

When to Use

  • Committing changes with appropriate messages
  • Pushing branches and creating pull requests
  • Cleaning up stale local branches
  • Full git workflow automation

Commands

/commit

Creates a git commit with an automatically generated commit message.

What it does:

  1. Analyzes current git status
  2. Reviews both staged and unstaged changes
  3. Examines recent commit messages to match repository style
  4. Drafts an appropriate commit message
  5. Stages relevant files
  6. Creates the commit

Usage:

/commit

Features:

  • Auto-generated messages matching repo style
  • Follows conventional commit practices
  • Avoids committing secrets (.env, credentials.json)
  • Includes attribution in commit message

/commit-push-pr

Complete workflow: commit → push → PR creation.

What it does:

  1. Creates a new branch (if currently on main)
  2. Stages and commits changes
  3. Pushes branch to origin
  4. Creates pull request using gh pr create
  5. Provides PR URL

Usage:

/commit-push-pr

Features:

  • Analyzes all commits in branch for PR description
  • Creates comprehensive PR descriptions with:
    • Summary (1-3 bullet points)
    • Test plan checklist
    • Attribution
  • Handles branch creation automatically

Requirements: GitHub CLI (gh) installed and authenticated

/clean-gone

Cleans up local branches deleted from remote.

What it does:

  1. Lists local branches with [gone] status
  2. Removes worktrees associated with [gone] branches
  3. Deletes stale local branches
  4. Reports what was cleaned up

Usage:

/clean-gone

When to use: After merging and deleting remote branches.

Best Practices

/commit

  • Review staged changes before committing
  • Let the system analyze and match your repo's style
  • Trust the automated message, verify it's accurate

/commit-push-pr

  • Ensure all changes are complete and tested
  • Review the PR description and edit if needed
  • Use when minimizing context switching

/clean-gone

  • Run periodically to keep branch list clean
  • Safe: only removes branches already deleted remotely
  • Helps maintain tidy local repository

Workflow Integration

Quick commit

/commit

Feature branch

/commit          # First commit
# more changes
/commit          # Second commit
/commit-push-pr  # Ready for PR

Maintenance

/clean-gone      # After merging PRs

Requirements

  • Git installed and configured
  • For /commit-push-pr: GitHub CLI (gh) installed and authenticated
  • Repository with a remote named origin

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