Claude Code Plugins

Community-maintained marketplace

Feedback

git-workflow

@ceshine/ceshine-agent-skills
0
0

Use when the user wants to interact with the local Git repository. Perform operations on local Git repositories: review staged changes, generate commit messages, examine commit history, create pull request descriptions, and more. (This skill will be expanded to cover additional Git workflows.)

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name git-workflow
description Always invoke this skill for any git-related request (commit messages, staging review, history, PR descriptions, etc.) so git workflows are handled consistently.

Git Workflow

Generate comprehensive pull request descriptions by analyzing git state: staged changes, commit history, and diffs between commits or branches.

Tool Selection

Try tools with these stems in their names first. Fall back to bash if unavailable (see Error Handling section for procedure):

MCP tools (preferred):

  • git_diff(ancestor) - Get diff from ancestor commit/branch to HEAD
  • git_cached_diff() - Get staged (cached) changes
  • git_commit_messages(ancestor) - Get commit messages from ancestor to HEAD

Bash fallbacks:

git diff <ancestor>..HEAD              # Diff between ancestor and HEAD
git diff --cached                      # Staged changes only
git log --oneline <ancestor>..HEAD     # Commit messages from ancestor to HEAD

Operations

1. Review Staged Changes

Perform a code review of staged modifications:

  1. Get cached changes: git_cached_diff() or git diff --cached
  2. Analyze the diff for:
    • Syntax errors: Missing semicolons, brackets, or typos
    • Logic issues: Broken conditions, off-by-one errors, null reference risks
    • Security concerns: Hardcoded secrets, SQL injection vectors, XSS patterns
    • Code quality: Deeply nested blocks, duplicated code, overly complex functions
    • Missing pieces: Unhandled edge cases, incomplete error handling
    • Style inconsistencies: Deviation from project's coding conventions
  3. Summarize findings:
    • Critical issues: Issues that should block the commit
    • Suggestions: Suggestions for improvement
    • Questions: Questions for the author

Present findings clearly, distinguishing between blocking issues and optional suggestions.

2. Generate Commit Message for Cached Changes

Create a descriptive commit message based on staged changes through an iterative review process:

Iterative Workflow:

  1. Review staged changes - Perform code review using the process described in the "1. Review Staged Changes" section.
  2. Present findings - Show issues and suggestions to user
  3. Wait for user - User may:
    • Edit the staged changes
    • Acknowledge issues but proceed
    • Ask for clarification
  4. Repeat review - If user modified changes, review again
  5. Generate commit message - Only after user approves

Generate Commit Message:

  1. Get cached changes: git_cached_diff() or git diff --cached
  2. Analyze the diff to identify:
    • What files changed
    • What type of changes (add, modify, delete)
    • Key modifications in the code
  3. Write to ./cache/commit_message.txt in conventional commit format (remove the file if it already exists before attempting to write to it):
    <type>(<scope>): <subject>

<body>

<footer>
    • Type: feat, fix, docs, style, refactor, test, chore
    • Scope: (optional) the area of code affected
    • Description: brief explanation of changes
    • Body: detailed description if needed
    • Footer: breaking changes or issue references
  4. Display the commit message to the user for review
  5. Allow user to edit if needed before committing

3. Generate Commit Message Summary

Extract commit messages to understand the history:

MCP: git_commit_messages(ancestor="<commit-or-branch>") Bash: git log --oneline <commit-or-branch>..HEAD

Returns commit hashes and messages, useful for:

  • Understanding changes across multiple commits
  • Identifying key features/bug fixes
  • Creating a changelog-style summary

4. Create Pull Request Description

Use the diff and recent commits to compose a structured PR body:

  1. Collect the diff for the target branch, preferably against the base (e.g., origin/main).
  2. Gather its commit messages to capture intent and progression.
  3. Extract:
    • Summary: A concise paragraph (1-2 sentences) describing the overall intent of the branch.
    • Key Changes: Bullet list that highlights the most important file edits or feature additions.
    • Commit History: Chronological list of commits (hash + message) so reviewers can trace the work.

Format suggestions:

## Summary
[Commit-driven overview]

## Key Changes
- `[File]`: [Primary modification]
- ...

Workflow Notes

  • Identify the merge base (usually origin/main or main).
  • Run git_diff(ancestor="origin/main") and git_commit_messages(ancestor="origin/main") to gather the data.
  • Parse and organize the collected information into the sections above before sharing with the user.

Error Handling

If git MCP tools are unavailable:

  1. Inform the user: "Git MCP tools not detected. These tools provide git diff, cached diff, and commit message functionality."
  2. Ask: "Would you like to proceed using bash commands instead?"
  3. If user confirms, use the bash fallbacks documented above
  4. If user declines, stop the workflow

If git commands fail:

  • Verify git repository
  • Check ancestor exists (commit hash or branch name)
  • Ensure working directory is clean or handle uncommitted changes