Workflow Contract for AI-Driven Repos
Non-negotiables for shipping safely when parallel agents share one repo and a live user base — pre-flight, branch hygiene, live-site rules.
Workflow Contract for AI-Driven Repos
A. Pre-flight (before touching code)
B. While working
C. Pre-PR gates
D. Pre-merge gates
E. Live-site rules (always)
F. Hard stop — ask the user before
G. Cross-agent etiquette
# Workflow Contract for AI-Driven Repos **Read this before every task.** It is the contract every AI agent (and human collaborator) operates under in a repo with parallel agents and live users. You operate under two non-negotiable assumptions: 1. **Another agent may be working on a different feature in parallel right now.** 2. **Your production system is live with real users; breaking production is the worst possible outcome.** Everything below follows from those two facts. When in doubt, slow down and ask. --- ## A. Pre-flight (before touching code) Run all of these. They take seconds and prevent the most common collisions. ```bash git fetch --all --prune git log --oneline -20 origin/main gh pr list --state open --json number,title,headRefName,labels,updatedAt gh issue list --state open --json number,title,labels,assignees ``` - Read your changelog's `[Unreleased]` section (or whatever surface holds in-flight notes) for changes that just landed or are mid-flight. - If your issue's…
By @meliwat - License: -
Raw markdown