finishing-a-development-branch SKILL.md skillA
finishing-a-development-branch from andreymudri/fleetmates is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add andreymudri/fleetmates/finishing-a-development-branch@git:20261103.344e4c8Pins git:20261103.344e4c8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- andreymudri/fleetmates
- Path
skills/finishing-a-development-branch/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261103.344e4c8, committed Nov 3, 2026
- First version recorded
- Sep 13, 2026
- Size
- 12,584 bytes
- Repository stars
- 3
- License
- MIT
Use when implementation is complete and needs integrating - re-runs the gate to verify each phase, then decides how the run branch lands.
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
# Finishing a Development Branch
Work is not finished because the code looks done. It is finished when a gate you just ran
says so — not when a record claims one already did.
## The completion gate
Work is not finished because the code looks done, and never because "the tests looked green"
or "the teammate said it was done" earlier in the conversation. Which check applies depends on
what state the run is in — check in this order.
### 1. Fleet run: `status.gates` is recorded
If `.fleetmates/<run-id>/status.json` exists and has a non-empty `status.gates`, this is a fleet
run — but a record in `status.gates` is a report written by the agents being enforced, and
`status.json` is agent-writable, so it is never trusted as evidence. A recorded `verdict` of
`PASS` proves nothing by itself:
{
"gates": {
"<phaseName>": {
"verdict": "PASS",
"failed": [],
"skipped": [],
"pending": [],
"recordedAt": 1785952191621
}
}
}
Use `status.gates` only to see which phases the run executed. For each of those phases,
**re-run the gate now**:
…Read the whole file at its exact version.
How to install
mdr add andreymudri/fleetmates/finishing-a-development-branch@sha256:78f373ad51fc89e9The line at the top of this page pins the label git:20261103.344e4c8, 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.
[](https://markdownregistry.com/a/art_ufwqcyjxzhekm55g)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Sep 13, 2026 and Nov 3, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261103.344e4c8 latest | 2026-11-03 | 344e4c8 | 12,584 B | A | view · diff |
| git:20261103.8e7ef94 | 2026-11-03 | 8e7ef94 | 12,061 B | A | view · diff |
| git:20261102.48716ca | 2026-11-02 | 48716ca | 10,773 B | A | view · diff |
| git:20261102.2b06149 | 2026-11-02 | 2b06149 | 10,075 B | A | view · diff |
| git:20260916.b8baf3a | 2026-09-16 | b8baf3a | 7,881 B | A | view · diff |
| git:20260913.46007d6 | 2026-09-13 | 46007d6 | 7,887 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12584 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
andreymudri/fleetmates · 3 stars · license MIT · pushed 2026-11-06 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_ufwqcyjxzhekm55g GET https://markdownregistry.com/api/v1/resolve?ref=andreymudri/fleetmates/finishing-a-development-branch GET https://markdownregistry.com/api/v1/blob/78f373ad51fc89e9db69954485ed7cd547d5804df119e3a3d12640f6af127ce0
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from andreymudri/fleetmates
Every file in andreymudri/fleetmates