developer SKILL.md skillA
developer from sgomez/developer-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sgomez/developer-skills/developer@git:20261012.009563cPins git:20261012.009563c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sgomez/developer-skills
- Path
skills/developer/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261012.009563c, committed Oct 12, 2026
- First version recorded
- Oct 7, 2026
- Size
- 8,130 bytes
- Repository stars
- 8
- License
- EUPL-1.2
Orchestrates unattended spec delivery — builds a spec's child issues in dependency order with code-author workers onto an integration branch (each build's model comes from the sub-issue's own ## Complexity section), then reviews the whole spec once with a diff-reviewer, runs a single fixer until CLEAN, and merges the spec PR per the repo's merge policy; a single issue gets the same build→review→fix on its own PR. The orchestration runs as a dynamic workflow (workflow.js next to this file)…
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
# Developer (launcher) The build → review → fix → merge pipeline runs as a **dynamic workflow**: `workflow.js`, next to this file. Its control flow — dependency order, the three-worker cap, fix cycles, the checks gate, serial merges, the conflict queue, escalation, wrap-up — is code, so no model re-reads a growing context on every worker result. Your part is small: publish the context docs, resolve the run config, launch the workflow, report what it returns. A spec with sub-issues is delivered on an **integration branch**, `agent/developer/spec-<N>`: each sub-issue is built from its tip and merged into it with no checks gate and no review of its own — the worker ran the project checks; then the **spec PR** (that branch into `main`) gets one whole-spec review, a single fixer — for its `[blocking]` findings until CLEAN, once for its `[fix]` findings when nothing blocks — and the one CI gate before it merges. Reviewing sub-issues one at a time misses how they fit together. A single issue, or one sub-issue on its own, gets its own PR into `main` and its own review. A local code host or tracker keeps that per-PR flow for specs too. ## Invoke ``` …
Read the whole file at its exact version.
How to install
mdr add sgomez/developer-skills/developer@sha256:8cf9b0e6cbb2f62aThe line at the top of this page pins the label git:20261012.009563c, 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_nov3f7edg7bh446r)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 7, 2026 and Oct 12, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.009563c latest | 2026-10-12 | 009563c | 8,130 B | A | view · diff |
| git:20261007.ae3a965 | 2026-10-07 | ae3a965 | 8,314 B | A | view · diff |
| git:20261007.bd0da28 | 2026-10-07 | bd0da28 | 8,213 B | A | view · diff |
| git:20261007.ecb5a32 | 2026-10-07 | ecb5a32 | 8,207 B | A | view · diff |
| git:20261007.f602cfc | 2026-10-07 | f602cfc | 8,156 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 (8130 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
sgomez/developer-skills · 8 stars · license EUPL-1.2 · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nov3f7edg7bh446r GET https://markdownregistry.com/api/v1/resolve?ref=sgomez/developer-skills/developer GET https://markdownregistry.com/api/v1/blob/8cf9b0e6cbb2f62ab260d16e7419749f4020b7d8ba11974b84aea8059346c11a
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 sgomez/developer-skills
Every file in sgomez/developer-skills