Skip to content

ComeOnOliver/skillshub / skills/0xlayerghost/solidity-agent-kit/git-workflow

git-workflow

Unverified

[AUTO-INVOKE] MUST be invoked BEFORE creating git commits, PRs, or code reviews. Covers Conventional Commits, PR templates, review requirements, and AI-assisted development rules. Trigger: any task involving git commit, git push, PR creation, or code review.

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
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 107kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 107kUpdated Claude CodeCodexVerifiedInstall