mcpField
G
git-workflow

git-workflow

github.com/0xlayerghostDevelopment4113 installsUpdated 2w ago
Repository

About git-workflow

A Git collaboration skill that defines commit, branch, pull request, review, and AI-assisted coding practices. It is intended for development teams that need consistent repository workflows, including specific review and testing requirements for contract changes.

Key features

  1. 01Conventional Commits guidance
  2. 02Review changes before staging
  3. 03Feature branch naming patterns
  4. 04Pull request content requirements
  5. 05Code review and AI coding rules

Use cases

  1. 01Preparing changes for a commit
  2. 02Creating a feature or fix branch
  3. 03Opening a pull request with required details
  4. 04Reviewing AI-generated or contract upgrade code

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/0xlayerghost/solidity-agent-kit --skill git-workflow

After installing, type/git-workflowin Claude Code to confirm it loaded.

Details

From the project README

Git Collaboration Standards

Language Rule

  • Always respond in the same language the user is using. If the user asks in Chinese, respond in Chinese. If in English, respond in English.

Commit Rules

Use Conventional Commits format: <type>: <short description>

TypeWhen to use
feat:New feature or contract
fix:Bug fix
refactor:Code restructure without behavior change
test:Add or update tests
docs:Documentation changes
chore:Build config, dependency updates, toolchain
security:Security fix or hardening
Commit Workflow
  1. Run git diff to review all changes before staging
  2. Stage specific files — avoid git add . to prevent committing .env or artifacts
  3. Write concise commit message describing the why, not the what
  4. Never add Co-Authored-By lines — commit messages should only contain the description
  5. Only commit — never git push unless explicitly requested
  6. Never push directly to main/master — always use feature branches

Branch Naming

PatternExample
feat/<name>feat/staking-pool
fix/<name>fix/reentrancy-guard
refactor/<name>refactor/token-structure

PR Requirements

Every PR must include:

SectionContent
Change descriptionWhat was changed and why
Test resultsforge test output (all pass)
Gas impactforge test --gas-report diff for changed functions
Deployment impactDoes this affect deployed contracts? Migration needed?
Review focusSpecific areas that need careful review

Code Review Rules

ScenarioRequirement
Standard changesMinimum 1 maintainer approval
Security-related changesMinimum 2 maintainer approvals
AI-generated codeMust pass manual review + forge test before merge
Contract upgradesRequires full team review + upgrade simulation on fork

AI Assistance Rules

  • AI-generated code must pass forge test before committing
  • Always review AI output for: correct import paths, proper access control, gas implications
  • Include relevant file paths and test cases in AI prompts for better results
  • Run forge fmt after AI generates code to ensure consistent formatting

Comments

Markdown supported