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

Git Helper

skill-joshuadavidthomas-opencode-agent-skills-git-helper · by joshuadavidthomas

Provides git workflow assistance, branch management, and commit message optimization

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

Install

$ agentstack add skill-joshuadavidthomas-opencode-agent-skills-git-helper

✓ 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 No
  • ✓ 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 Helper? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Git Helper

A comprehensive skill for git workflow management and best practices.

Quick Start

Use this skill when you need help with:

  • Branch creation and management
  • Commit message formatting
  • Git workflow optimization
  • Repository maintenance

Common Workflows

Creating a New Feature Branch

git checkout -b feature/your-feature-name
git push -u origin feature/your-feature-name

Writing Good Commit Messages

Follow the conventional commit format:

type(scope): description

[optional body]

[optional footer]

Types: feat, fix, docs, style, refactor, test, chore

Git Cleanup Commands

Remove stale branches

git remote prune origin

Clean up local branches

git branch -d branch-name

Scripts

This skill includes helper scripts:

• create-branch.sh - Creates new feature branches with proper naming • commit-check.sh - Validates commit message format • cleanup.sh - Removes stale branches

Best Practices

  1. Always pull latest changes before creating branches
  2. Use descriptive branch names with prefixes (feature/, bugfix/, hotfix/)
  3. Write atomic commits (one logical change per commit)
  4. Keep commit messages under 72 characters for the subject line

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 Agent Skills