commit-commands

Streamline your git workflow with simple commands for committing, pushing, and creating pull requests

Author: Anthropic Category: productivity

Installation

/plugin marketplace add giginet/claude-plugins-official
/plugin install commit-commands@claude-plugins-official
claude plugin marketplace add giginet/claude-plugins-official
claude plugin install commit-commands@claude-plugins-official

Commands

NameDescription
clean_gone Cleans up all git branches marked as [gone] (branches that have been deleted on the remote but still exist locally), including removing associated worktrees.

Your Task

You need to execute the following bash commands to clean up stale local branches that have been deleted from the remote repository.

Commands to Execute

  1. First, list branches to identify any with [gone] status Execute this command: bash git branch -v

Note: Branches with a '+' prefix have associated worktrees and must have their worktrees removed before deletion.

  1. Next, identify worktrees that need to be removed for [gone] branches Execute this command: bash git worktree list

  2. Finally, remove worktrees and delete [gone] branches (handles both regular and worktree branches) Execute this command: bash # Process all [gone] branches, removing '+' prefix if present git branch -v | grep '\[gone\]' | sed 's/^[+* ]//' | awk '{print $1}' | while read branch; do echo "Processing branch: $branch" # Find and remove worktree if it exists worktree=$(git worktree list | grep "\\[$branch\\]" | awk '{print $1}') if [ ! -z "$worktree" ] && [ "$worktree" != "$(git rev-parse --show-toplevel)" ]; then echo " Removing worktree: $worktree" git worktree remove --force "$worktree" fi # Delete the branch echo " Deleting branch: $branch" git branch -D "$branch" done

Expected Behavior

After executing these commands, you will:

  • See a list of all local branches with their status
  • Identify and remove any worktrees associated with [gone] branches
  • Delete all branches marked as [gone]
  • Provide feedback on which worktrees and branches were removed

If no branches are marked as [gone], report that no cleanup was needed.

commit-push-pr Commit, push, and open a PR
allowed-toolsBash(git checkout --branch:*), Bash(git add:*), Bash(git status:*), Bash(git push:*), Bash(git commit:*), Bash(gh pr create:*)

Context

  • Current git status: !git status
  • Current git diff (staged and unstaged changes): !git diff HEAD
  • Current branch: !git branch --show-current

Your task

Based on the above changes:

  1. Create a new branch if on main
  2. Create a single commit with an appropriate message
  3. Push the branch to origin
  4. Create a pull request using gh pr create
  5. You have the capability to call multiple tools in a single response. You MUST do all of the above in a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.
commit Create a git commit
allowed-toolsBash(git add:*), Bash(git status:*), Bash(git commit:*)

Context

  • Current git status: !git status
  • Current git diff (staged and unstaged changes): !git diff HEAD
  • Current branch: !git branch --show-current
  • Recent commits: !git log --oneline -10

Your task

Based on the above changes, create a single git commit.

You have the capability to call multiple tools in a single response. Stage and create the commit using a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.

README

Commit Commands Plugin

Streamline your git workflow with simple commands for committing, pushing, and creating pull requests.

Overview

The Commit Commands Plugin automates common git operations, reducing context switching and manual command execution. Instead of running multiple git commands, use a single slash command to handle your entire workflow.

Commands

/commit

Creates a git commit with an automatically generated commit message based on staged and unstaged changes.

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

Usage:

/commit

Example workflow:

# Make some changes to your code
# Then simply run:
/commit

# Claude will:
# - Review your changes
# - Stage the files
# - Create a commit with an appropriate message
# - Show you the commit status

Features: - Automatically drafts commit messages that match your repo's style - Follows conventional commit practices - Avoids committing files with secrets (.env, credentials.json) - Includes Claude Code attribution in commit message

/commit-push-pr

Complete workflow command that commits, pushes, and creates a pull request in one step.

What it does: 1. Creates a new branch (if currently on main) 2. Stages and commits changes with an appropriate message 3. Pushes the branch to origin 4. Creates a pull request using gh pr create 5. Provides the PR URL

Usage:

/commit-push-pr

Example workflow:

# Make your changes
# Then run:
/commit-push-pr

# Claude will:
# - Create a feature branch (if needed)
# - Commit your changes
# - Push to remote
# - Open a PR with summary and test plan
# - Give you the PR URL to review

Features: - Analyzes all commits in the branch (not just the latest) - Creates comprehensive PR descriptions with: - Summary of changes (1-3 bullet points) - Test plan checklist - Claude Code attribution - Handles branch creation automatically - Uses GitHub CLI (gh) for PR creation

Requirements: - GitHub CLI (gh) must be installed and authenticated - Repository must have a remote named origin

/clean_gone

Cleans up local branches that have been deleted from the remote repository.

What it does: 1. Lists all local branches to identify [gone] status 2. Identifies and removes worktrees associated with [gone] branches 3. Deletes all branches marked as [gone] 4. Provides feedback on removed branches

Usage:

/clean_gone

Example workflow:

# After PRs are merged and remote branches are deleted
/clean_gone

# Claude will:
# - Find all branches marked as [gone]
# - Remove any associated worktrees
# - Delete the stale local branches
# - Report what was cleaned up

Features: - Handles both regular branches and worktree branches - Safely removes worktrees before deleting branches - Shows clear feedback about what was removed - Reports if no cleanup was needed

When to use: - After merging and deleting remote branches - When your local branch list is cluttered with stale branches - During regular repository maintenance

Installation

This plugin is included in the Claude Code repository. The commands are automatically available when using Claude Code.

Best Practices

Using /commit

  • Review the staged changes before committing
  • Let Claude analyze your changes and match your repo's commit style
  • Trust the automated message, but verify it's accurate
  • Use for routine commits during development

Using /commit-push-pr

  • Use when you're ready to create a PR
  • Ensure all your changes are complete and tested
  • Claude will analyze the full branch history for the PR description
  • Review the PR description and edit if needed
  • Use when you want to minimize context switching

Using /clean_gone

  • Run periodically to keep your branch list clean
  • Especially useful after merging multiple PRs
  • Safe to run - only removes branches already deleted remotely
  • Helps maintain a tidy local repository

Workflow Integration

Quick commit workflow:

# Write code
/commit
# Continue development

Feature branch workflow:

# Develop feature across multiple commits
/commit  # First commit
# More changes
/commit  # Second commit
# Ready to create PR
/commit-push-pr

Maintenance workflow:

# After several PRs are merged
/clean_gone
# Clean workspace ready for next feature

Requirements

  • Git must be installed and configured
  • For /commit-push-pr: GitHub CLI (gh) must be installed and authenticated
  • Repository must be a git repository with a remote

Troubleshooting

/commit creates empty commit

Issue: No changes to commit

Solution: - Ensure you have unstaged or staged changes - Run git status to verify changes exist

/commit-push-pr fails to create PR

Issue: gh pr create command fails

Solution: - Install GitHub CLI: brew install gh (macOS) or see GitHub CLI installation - Authenticate: gh auth login - Ensure repository has a GitHub remote

/clean_gone doesn't find branches

Issue: No branches marked as [gone]

Solution: - Run git fetch --prune to update remote tracking - Branches must be deleted from the remote to show as [gone]

Tips

  • Combine with other tools: Use /commit during development, then /commit-push-pr when ready
  • Let Claude draft messages: The commit message analysis learns from your repo's style
  • Regular cleanup: Run /clean_gone weekly to maintain a clean branch list
  • Review before pushing: Always review the commit message and changes before pushing

Author

Anthropic (support@anthropic.com)

Version

1.0.0

License

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.