Spec-Density Scorecard and 12 Agent Spec Templates
agent spec templates scored by the WOWHOW Spec-Density rubric — 12 ready-to-fill templates across task types, eliminate agent drift on first run.
Multi-agent git workflow kit that enforces exactly one push per session — preventing double-deploys, 502s, and race conditions in AI-assisted codebases.
Multi-agent git workflow kit that enforces exactly one push per session — preventing double-deploys, 502s, and race conditions in AI-assisted codebases.
Three concurrent AI agents, each doing meaningful work — and then three near-simultaneous pushes that trigger three parallel deploys, each one stepping on the last. That is the exact failure mode this kit exists to prevent. The Single-Push Multi-Agent Git Workflow Kit is a WOWHOW framework for teams and solo developers who orchestrate multiple AI coding agents (Claude Code, GitHub Copilot Workspace, Cursor background agents, or custom Agent SDK pipelines) against a single shared repository. It packages a battle-tested pre-push gate script, the WOWHOW Single-Push Protocol playbook, and a coordination checklist into one deployable zip.
.githooks/pre-push. Runs a configurable build verification command (defaults to next build --no-lint), checks for an in-progress deploy lock on the remote host, and aborts the push if a concurrent deploy is already running. Includes a SKIP_BUILD=1 emergency override for genuine hotfixes. Not a wrapper — the actual hook logic with comments explaining every guard.cancel-in-progress: false setting (not true — the difference matters: cancelling in-progress lets intermediate pushes win over the latest, which is the opposite of what you want) and a comment explaining the queuing behavior.Start with the README to understand which of the three failure classes applies to your stack. Most projects hit Class 1 (concurrent GH Actions SSH sessions) or Class 2 (agent worktrees pushing independently). Class 3 (split-brain cron + CI racing) requires the full playbook.
Copy pre-push-gate.sh to .githooks/pre-push and run chmod +x .githooks/pre-push && git config core.hooksPath .githooks. Edit the four config variables at the top of the file: your build command, your lock file path, your VPS SSH alias (or leave blank to skip remote lock check), and your SKIP_BUILD env var name.
Paste the concurrency snippet from workflow-concurrency-snippet.yml into your deploy workflow under the jobs: top-level key — not inside a job. If you already have a concurrency block, compare it against the snippet: the group name must be consistent across all workflows that touch the same deploy target.
Before your next multi-agent session, run through agent-coordination-checklist.md at the end, not the beginning — it is a pre-push gate, not a session-start ritual. The checklist assumes agents have already committed their work into a staging branch; it validates the merge and push are safe.
Read single-push-protocol.md once in full. The six rules are short. The incident notes are specific. You will recognize at least one scenario from your own deploy history.
docker compose down and docker compose upThe pre-push hook in this kit does not require any additional tooling beyond bash and git. The GitHub Actions snippet works with any self-hosted or cloud runner. Both are designed to stay in place permanently — not as temporary scaffolding. Browse more developer workflow tools at wowhow.cloud/browse, or check the free tools collection at wowhow.cloud/tools for related utilities.
Included Files
No reviews yet
Be the first to share your experience with this product
one-time payment, yours forever
Category
Claude Code