How do I install the Dev Flow Commit Merge skill?

Run npx skillmds@latest add earayu/dev-flow-commit-merge in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dev Flow Commit Merge safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dev Flow Commit Merge?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dev Flow Commit Merge free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dev Flow Commit Merge?

earayu (@earayu) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dev Flow Commit Merge by earayu — Agent Skill

Name: Dev Flow Commit Merge
Author: earayu

File contents

Dev Flow: commit, branch, merge

Use this skill whenever you are about to commit, open a PR, or merge.

Commit identity (never hand-craft)

Shared boxes often have no git identity → bare git commit fails with Author identity unknown. Do not git config --global. Identity comes from agent-tools.yaml (identity.*). Prefer the wrapped recipe; if invoking git directly as a fallback:

git -c user.name="$IDENTITY_NAME" -c user.email="$IDENTITY_EMAIL" commit -F - <<'EOF'
<subject>

<body>

<pr_owner_line from config, if set>

<commit_trailer from config, if set>
EOF

Multi-line / non-ASCII / backticks in the message → ALWAYS heredoc (-F -). Never -m "..." with backticks — the shell mangles it into a truncated commit.
PR body first line MUST be identity.pr_owner_line when set.

Branch hygiene (check BEFORE every commit)

git branch --show-current

Real incident: a commit landed on local main because the agent assumed it was on the feature branch. Recovery:

git branch -f <feature-branch> <commit-sha>   # or: git cherry-pick <sha>
git checkout <feature-branch>
git branch -f main origin/main                # un-pollute local main

Remote main is only polluted if you git push from main — never push from main.

PR + merge

One change = one branch = one PR.
Before merge, the branch MUST be caught up with the default branch: git merge-base --is-ancestor origin/<default> HEAD. If behind, git merge origin/<default> first — a stale branch either blocks merge or drags an out-of-date tree (and can mask CI matrix drift).
Merge per github.merge config: squash + delete-branch + verify the returned merge-commit oid. Honor require_green.
Only the work owner reports merge status; don't echo others' merges.

---name: dev-flow-commit-mergedescription: Follow this before any commit, PR, or merge. Covers commit identity, branch hygiene, and merge mechanics so agents stop re-deriving the flow and wasting tokens.---# Dev Flow: commit, branch, mergeUse this skill whenever you are about to commit, open a PR, or merge.## Commit identity (never hand-craft)Shared boxes often have no git identity → bare `git commit` fails with`Author identity unknown`. Do **not** `git config --global`. Identitycomes from `agent-tools.yaml` (`identity.*`). Prefer the wrapped recipe;if invoking git directly as a fallback:```shgit -c user.name="$IDENTITY_NAME" -c user.email="$IDENTITY_EMAIL" commit -F - <<'EOF'<subject><body><pr_owner_line from config, if set><commit_trailer from config, if set>EOF```- Multi-line / non-ASCII / backticks in the message → ALWAYS heredoc (`-F -`). Never `-m "..."` with backticks — the shell mangles it into a truncated commit.- PR body first line MUST be `identity.pr_owner_line` when set.## Branch hygiene (check BEFORE every commit)```shgit branch --show-current```Real incident: a commit landed on local `main` because the agentassumed it was on the feature branch. Recovery:```shgit branch -f <feature-branch> <commit-sha> # or: git cherry-pick <sha>git checkout <feature-branch>git branch -f main origin/main # un-pollute local main```Remote `main` is only polluted if you `git push` from `main` — neverpush from `main`.## PR + merge- One change = one branch = one PR.- Before merge, the branch MUST be caught up with the default branch: `git merge-base --is-ancestor origin/<default> HEAD`. If behind, `git merge origin/<default>` first — a stale branch either blocks merge or drags an out-of-date tree (and can mask CI matrix drift).- Merge per `github.merge` config: squash + delete-branch + verify the returned merge-commit oid. Honor `require_green`.- Only the work owner reports merge status; don't echo others' merges.

Frequently asked questions

Dev Flow Commit Merge