All git and GitHub operations go through gw — never use raw git or gh commands directly.
Works with
Grove Wrap adds safety tiers, Conventional Commits enforcement, protected branch guards, and agent-safe defaults.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongit-workflowsExecute the skills CLI command in your project's root directory to begin installation:
Fetches git-workflows from autumnsgrove/groveengine and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate git-workflows. Access via /git-workflows in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
2
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
2
stars
All git and GitHub operations go through gw — never use raw git or gh commands directly.
Grove Wrap adds safety tiers, Conventional Commits enforcement, protected branch guards, and agent-safe defaults.
Activate this skill when:
gw enforces a three-tier safety model:
| Tier | Flag Required | Examples |
|---|---|---|
| READ | None | gw git status, gw git log, gw gh pr list |
| WRITE | --write |
gw git commit, gw git push, gw git pull, gw gh pr create |
| DANGEROUS | --write --force |
gw git reset, gw git force-push, gw git rebase |
Protected branches (main, master, production, staging) can NEVER be force-pushed, even with --force.
Agent mode (auto-detected for Claude Code): stricter row limits, force operations blocked, all operations audit-logged.
Dry run any command with --dry-run to preview what would happen.
gw validates commit messages against Conventional Commits automatically. Format:
<type>(<optional scope>): <brief description>
<optional body>
<optional footer>
| Type | Purpose | Example |
|---|---|---|
feat |
New feature | feat: add user authentication |
fix |
Bug fix | fix: correct validation error |
docs |
Documentation | docs: update README |
style |
Code formatting | style: format with prettier |
refactor |
Code restructure | refactor: extract helper function |
test |
Add/modify tests | test: add auth tests |
chore |
Maintenance | chore: update dependencies |
perf |
Performance | perf: optimize query speed |
ci |
CI/CD changes | ci: fix deploy workflow |
Breaking changes: Add an exclamation mark after the type, e.g. feat!: replace XML config with YAML
gw git status # Enhanced git status
gw git log # Formatted commit history
gw git log --limit 20 # Last 20 commits
gw git diff # Show changes
gw git diff --staged # Show staged changes
gw git blame file.ts # Blame with context
gw git show abc123 # Show commit details
--write)gw git add --write . # Stage files
gw git add --write src/lib/thing.ts # Stage specific file
gw git commit --write -m "feat: add new feature" # Commit (validates conventional commits!)
gw git push --write # Push to remote
gw git pull --write # Pull from remote
gw git pull --write --rebase # Pull with rebase strategy
gw git branch --write feature/new-thing # Create branch
gw git switch --write feature/new-thing # Switch branches
gw git stash --write # Stash changes
gw git stash --write pop # Pop stash
gw git unstage --write file.ts # Unstage files
--write --force)gw git push --write --force # Force push (blocked to protected branches!)
gw git reset --write --force HEAD~1 # Hard reset
gw git rebase --write --force main # Rebase onto main
gw git merge --write --force feature # Merge branches
These combine common multi-step operations into single commands:
# Quick save: stage all + WIP commit
gw git save --write
# Quick sync: fetch + rebase + push
gw git sync --write
# WIP commit that skips hooks
gw git wip --write
# Undo last commit (keeps changes staged)
gw git undo --write
# Amend last commit message
gw git amend --write -m "better message"
# FAST MODE: skip ALL hooks, commit + push in one shot
gw git fast --write -m "fix: emergency hotfix"
feature/feature-name # New features
fix/bug-description # Bug fixes
experiment/new-idea # Experiments
release/v1.0.0 # Releases
# Create and switch to feature branch
gw git branch --write feature/user-auth
gw git switch --write feature/user-auth
# Work and commit
gw git add --write .
gw git commit --write -m "feat: add JWT authentication"
# Push and create PR
gw git push --write
gw gh pr create --write --title "feat: add JWT authentication"
# Reading (always safe)
gw gh pr list # List open PRs
gw gh pr view 123 # View PR details
gw gh pr status # PR status (CI, reviews, etc.)
# Writing (needs --write)
gw gh pr create --write --title "feat: new thing" --body "Description"
gw gh pr comment --write 123 "LGTM!"
gw gh pr merge --write 123 # Merge PR (prompts for confirmation)
# Reading (always safe)
gw gh issue list # List open issues
gw gh issue view 456 # View issue details
# Writing (needs --write)
gw gh issue create --write --title "Bug: thing broke"
gw gh issue close --write 456
# Reading (always safe)
gw gh run list # List recent runs
gw gh run view 12345678 # View run details
gw gh run watch 12345678 # Watch a running workflow
# Writing (needs --write)
gw gh run rerun --write 12345678 --failed # Rerun failed jobs
gw gh run cancel --write 12345678 # Cancel a run
# GET requests (always safe)
gw gh api repos/AutumnsGrove/Lattice
# POST/PATCH (needs --write)
gw gh api --write repos/{owner}/{repo}/labels -X POST -f name="bug"
# DELETE (needs --write --force)
gw gh api --write --force repos/{owner}/{repo}/labels/old -X DELETE
# Check rate limit status
gw gh rate-limit
gw gh project list # List project boards
gw gh project view # View current project
gw git commit --write -m "feat: add dark mode toggle
- Implement theme switching logic
- Add localStorage persistence
- Update CSS variables"
gw git commit --write -m "fix: correct timezone handling bug
Fixes off-by-one error in date calculations.
Closes #123"
gw git commit --write -m "feat!: replace XML config with YAML
BREAKING CHANGE: XML configuration no longer supported.
See docs/migration.md for upgrade instructions."
These commands are specifically designed for agentic workflows:
gw context # One-shot session snapshot (rich output)
gw --json context # JSON snapshot (branch, changes, packages, issues)
# Stage all + format + check + commit + push in ONE command
gw git ship --write -a -m "feat: implement feature"
# Equivalent to: gw git add --write . && gw git ship --write -m "..."
gw git pr-prep # Full PR readiness report
gw --json git pr-prep # JSON: commits, files, packages, suggested title
gw ci --affected # Only check packages with changes
gw ci --affected --fail-fast # Fast feedback: stop on first failure
gw ci --diagnose # Structured error output when steps fail
gw --json ci --affected # JSON with parsed error details
# Create multiple issues from JSON
gw gh issue batch --write --from-json issues.json
echo '[{"titleMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
git-workflows reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added git-workflows from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for git-workflows matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: git-workflows is the kind of skill you can hand to a new teammate without a long onboarding doc.
git-workflows fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
git-workflows has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend git-workflows for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added git-workflows from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
git-workflows reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for git-workflows matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 51