AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Git Workflow

skill-comeonoliver-skillshub-git-workflow · by ComeOnOliver

[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.

↗ Website ↗ Repository
— No reviews yet
0 installs
14 views
0.0% view→install

Install

$ agentstack add skill-comeonoliver-skillshub-git-workflow

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ● Environment & secrets Used
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Git Workflow? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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 | When 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

| Pattern | Example | |---------|---------| | feat/ | feat/staking-pool | | fix/ | fix/reentrancy-guard | | refactor/ | refactor/token-structure |

PR Requirements

Every PR must include:

| Section | Content | |---------|---------| | Change description | What was changed and why | | Test results | forge test output (all pass) | | Gas impact | forge test --gas-report diff for changed functions | | Deployment impact | Does this affect deployed contracts? Migration needed? | | Review focus | Specific areas that need careful review |

Code Review Rules

| Scenario | Requirement | |----------|------------| | Standard changes | Minimum 1 maintainer approval | | Security-related changes | Minimum 2 maintainer approvals | | AI-generated code | Must pass manual review + forge test before merge | | Contract upgrades | Requires 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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in AI & ML