dev-git

Stage files, write attributed commit messages, and choose merge or PR integration paths.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/mnazaal/dotfiles --skill dev-git-mnazaal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-git
Source: https://github.com/mnazaal/dotfiles/tree/main/.agents/skills/dev-git
Command: npx skills add https://github.com/mnazaal/dotfiles --skill dev-git-mnazaal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Committing work with Git involves many easy-to-miss pitfalls: accidentally staging secrets or unrelated files, misattributing AI contributions, committing half-finished refactors, or pushing to protected branches. This Skill enforces a disciplined commit and integration workflow so every commit is accurate, honest, and safe. ## Core Features & Use Cases - Safe Staging and Committing: Stage specific files by name, verify the staged diff, and write imperative commit messages with honest Assisted-by: AI attribution trailers instead of Co-Authored-By:. - Integration Decision Workflow: Dry-run merges with git merge-tree, verify readiness evidence, and present merge/PR/park/abandon options before executing any integration write. - Guardrail Compliance: Respect branch-prefix hooks and protected branches by presenting commands for the user to run rather than bypassing guards with --no-verify or force-push. - Use Case: After finishing a feature, ask the assistant to commit the work — it reviews the diff, stages only intended files, runs verification evidence, writes a conventional commit with attribution, and recommends whether to merge or open a PR. ## Quick Start Ask the assistant to review the current changes, stage the relevant files, and create a properly attributed commit, then recommend an integration path.

Frequently Asked Questions about dev-git

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a good git commit message with AI attribution?▼

Use an imperative subject under 50 characters, optionally with a Conventional Commits prefix like feat: or fix:. Add a body explaining why the change exists, and include an Assisted-by: trailer for each AI tool that substantially contributed — never Co-Authored-By:, which misattributes copyright.

How to stage specific files in git instead of git add -A?▼

Stage files individually by name with git add <path> after reviewing git diff HEAD. Run git status before each commit since the index accumulates everything staged so far, and use git restore --staged <path> to unstage anything that should not be included.

How do I check for merge conflicts before merging a branch?▼

Run git merge-tree $(git merge-base <target> <branch>) <target> <branch> to dry-run the merge without touching the working tree. Inspect the output for conflict markers before recommending or executing the actual merge.

What should I do when a git hook rejects a commit on the wrong branch?▼

Check the current branch with git branch --show-current, then create a fresh branch matching the required prefix and commit there. Never bypass the guard with --no-verify or unset the hook — branch-prefix guards exist to route agent work onto agent branches.

When should I not amend or force-push a git commit?▼

Never amend a pushed commit or force-push without explicit user confirmation, since both rewrite shared history. History rewriting, reflog recovery, and revert-versus-reset decisions belong to a dedicated git rescue workflow, not the standard commit path.