Squad branching model: dev-first workflow with insiders preview channel.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## Context
Squad uses a three-branch model. **All feature work starts from `dev`, not `main`.**
| Branch | Purpose | Publishes |
|--------|---------|-----------|
| `main` | Released, tagged, in-npm code only | `npm publish` on tag |
| `dev` | Integration branch — all feature work lands here | `npm publish --tag preview` on merge |
| `insiders` | Early-access channel — synced from dev | `npm publish --tag insiders` on sync |
## Branch Naming Convention
Issue branches MUST use: `squad/{issue-number}-{kebab-case-slug}`
Examples:
- `squad/195-fix-version-stamp-bug`
- `squad/42-add-profile-api`
## Workflow for Issue Work
1. **Branch from dev:**
```bash
git checkout dev
git pull origin dev
git checkout -b squad/{issue-number}-{slug}
```
2. **Mark issue in-progress:**
```bash
gh issue edit {number} --add-label "status:in-progress"
```
3. **Create draft PR targeting dev:**
```bash
gh pr create --base dev --title "{description}" --body "Closes #{issue-number}" --draft
```
4. **Do the work.** Make changes, write tests, commit with issue reference.
5. **Push and mark ready:**
```bash
git push -u origin squad/{issue-number}-{slug}
…
The line at the top of this page pins the label git:20260910.9cf5842, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (6259 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
bradygaster/squad · 3,298 stars · license MIT · pushed 2026-10-22 · branch dev
API
GET https://markdownregistry.com/api/v1/artifacts/art_clkb664bebypf6fs
GET https://markdownregistry.com/api/v1/resolve?ref=bradygaster/squad/git-workflow
GET https://markdownregistry.com/api/v1/blob/b85373cb599d07bd13bf52939e9167df1cf5b1d16cb23d8913148afac7d6f50b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
bradygaster/squad · .copilot/skills/action-skill-contracts/SKILL.md · Author deterministic skills for operations that change state or invoke external tools
bradygaster/squad · .copilot/skills/agent-collaboration/SKILL.md · Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
bradygaster/squad · .copilot/skills/architectural-proposals/SKILL.md · How to write comprehensive architectural proposals that drive alignment before code is written
mindrally/skills · git-workflow/SKILL.md · Git conventions and workflow guidelines using Conventional Commits, branching strategies, and best practices for…
