staging SKILL.md skillA
staging from j0ruge/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add j0ruge/skills/staging@v3.3.0Pins v3.3.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- j0ruge/skills
- Path
plugins/deploy/skills/staging/SKILL.md- Versions recorded
- 4
- Latest version
- v3.3.0, committed Oct 15, 2026
- First version recorded
- Oct 6, 2026
- Size
- 16,693 bytes
- Repository stars
- 13
- License
- none declared
Promote code to staging (and on to production) through the repo's real CD pipeline. Reads each workflow's `on.push.branches` and `runs-on` instead of assuming — the wrong branch can deploy production, and a hosted job under a billing block never starts. Waits for CI green on the exact commit, promotes by PR merge commit, watches the run, then proves the deploy by the data. Triggers — deploy staging, promote to staging, subir para staging, CD pipeline, cd-staging, promover para produção.
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
## Deploy to Staging
Promote the current work to the staging environment through whatever CD pipeline
the repository actually has.
**Read this before anything else.** A deploy command is one `git push` away from
shipping to production. Branch names carry no universal meaning: in one repo
`develop` triggers staging and `main` is just kept in sync; in another the chain
is `develop → staging → main`, where pushing `main` deploys to real users. An
earlier version of this skill hardcoded the first topology, so running it in a
repo of the second kind would have deployed **production** while reporting
"staging". That is the failure this workflow exists to prevent.
So the first step is never `git push` — it is reading the workflows to learn
which branch triggers what. Everything else follows from that map.
### Step 0 — Discover the topology (never assume it)
Print the trigger block of every workflow and build the branch → pipeline map:
```bash
for f in .github/workflows/*.y*ml; do
echo "── $f"
awk '/^on:/{flag=1} flag{print} /^permissions:|^env:|^jobs:/{if(flag) exit}' "$f" | head -12
echo
done
```
…Read the whole file at its exact version.
How to install
mdr add j0ruge/skills/staging@sha256:4f17452ebea84dd3The line at the top of this page pins the label v3.3.0, 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_26uyqujj2ixkzjvj)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 6, 2026 and Oct 15, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v3.3.0 latest | 2026-10-15 | eb1c159 | 16,693 B | A | view · diff |
| v3.2.0 | 2026-10-14 | 7edbe84 | 16,184 B | A | view · diff |
| v3.1.0 | 2026-10-13 | 6157611 | 15,600 B | A | view · diff |
| v3.0.0 | 2026-10-06 | 8df09be | 14,805 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 (16693 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
j0ruge/skills · 13 stars · license none declared · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_26uyqujj2ixkzjvj GET https://markdownregistry.com/api/v1/resolve?ref=j0ruge/skills/staging GET https://markdownregistry.com/api/v1/blob/4f17452ebea84dd3c9ac6dcd1ae9017fb1529c277ab41639a3f9658485b713ed
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.