0xlayerghost/solidity-agent-kit104 installs

git-workflow

Q: How do I install this agent skill?

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

Q: Is this agent skill safe to install?

Review the displayed partner audits, complete source, permissions, dependencies, and exact revision before installing.

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

How do I install this agent skill?

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

view source ↗

Is this agent skill safe to install?

Gen Agent Trust Hubpass
This skill defines standard Git collaboration and AI-assisted development workflows. It promotes secure practices such as excluding .env files from commits and requiring test verification. The skill inherently processes external data from git diffs and test results, which is a standard operational surface.
Socketpass
No alerts
Snykpass
Risk: LOW · No issues
Runlayerwarn
1/1 file flagged
ZeroLeakspass
Score: 93/100 · 2 sections analyzed

What does this agent skill do?

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>

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

Run git diff to review all changes before staging
Stage specific files — avoid git add . to prevent committing .env or artifacts
Write concise commit message describing the why, not the what
Never add Co-Authored-By lines — commit messages should only contain the description
Only commit — never git push unless explicitly requested
Never push directly to main/master — always use feature branches

Branch Naming

Pattern	Example
`feat/<name>`	`feat/staking-pool`
`fix/<name>`	`fix/reentrancy-guard`
`refactor/<name>`	`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

How can the creator link this skill?

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/0xlayerghost/solidity-agent-kit/git-workflow">View git-workflow on skillZs</a>