Automate safe commit workflows with scope inference and push/land actions.
npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill commit-zillabunny
Please help me install this Agent Skill. Skill: commit Source: https://github.com/zillabunny/GoblinVolleyball-1.1/tree/main/.claude/skills/commit Command: npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill commit-zillabunny
This Skill provides a safe commit workflow that helps teams avoid accidentally including unrelated changes by inferring scope from diffs and supports optional push or land operations to integrate changes cleanly.
Demonstrate a safe, scope-aware commit by performing a commit with a chosen scope and optionally using push or land.
High-intent search queries and answers about installing and using this skill.
To keep a git commit history clean in collaborative repositories, use a scope-aware commit workflow that infers scope from diffs and separates unrelated changes. This prevents cross-contamination and ensures targeted commits that minimize impact on other developers.
To avoid accidentally committing unrelated changes in a worktree, apply staging guardrails that classify related versus unrelated file modifications. This enforces strict staging discipline and ensures only scoped changes are handed off safely.
Yes, you can automatically infer a commit scope from your git diff when no explicit scope is provided. The workflow parses changes and traces dependencies to derive a targeted scope, ensuring the commit accurately represents the underlying modifications.
The best way to manage push and land actions for worktree commits is using an automated workflow that supports both remote pushes and local landings. This handles integration cleanly and maintains clear explanations for each collaboration-safe handoff.
Yes, a scope-aware commit workflow explicitly supports multiple developers working on the same repository. It creates targeted commits that capture intent, enforces staging discipline, and minimizes the impact of your changes on others.
jk278Analyze git repositories to summarize commit history and file changes.
mhattingpeteStage, commit, and push code changes with conventional commit messages.
nanorepublicaValidate code against centralized global tech stack standards.
JannaelGenerates Git commit messages adhering to Conventional Commits format with strict subject and body rules.
