propagate-changes SKILL.md skillA
propagate-changes from tomzx/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tomzx/agents/propagate-changes@git:20261007.b35fc4bPins git:20261007.b35fc4b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tomzx/agents
- Path
skills/propagate-changes/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261007.b35fc4b, committed Oct 7, 2026
- First version recorded
- Sep 21, 2026
- Size
- 22,580 bytes
- Repository stars
- 12
- License
- MIT
Run a bidirectional propagation pass over the SDLC artifact chain after a change, updating the artifacts that depend on the change (downward) and re-checking the premises the change depends on (upward). Use when the user says /propagate-changes, "propagate changes", "propagate this change", "bring the artifacts back in sync", or wants consistency restored in both directions across issue, requirements, specification, plan, tasks, tests, code, and documentation after a change.
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
# Propagate Changes A change made in one artifact invalidates two things at once: the artifacts built from it, and the artifacts it was built from. The forward `/sdlc` pipeline propagates intent downstream, and each `review-*` skill checks one adjacent pair in isolation. This skill runs one propagation pass in both directions along the artifact graph. Downward, it updates dependents: every artifact that still describes the old version is rewritten when the resolution follows from the change. Upward, it questions premises: every artifact the change depends on is re-checked, and drift is flagged for a human decision instead of being resolved by guesswork. Wherever two connected artifacts disagree in a way that admits more than one resolution, the pass raises a question rather than picking a side. ## Prerequisites - Working directory is the root of the repository - A populated `.sdlc/` directory (run `/sync-sdlc` first if absent) - At least one feature under `.sdlc/features/N-<slug>/` with artifacts present - Read access to the codebase - Read any files present under `.sdlc/context/` for project-level context, and apply their style rules to rewritten artifacts and the report …
Read the whole file at its exact version.
How to install
mdr add tomzx/agents/propagate-changes@sha256:0fb3eac612d2e796The line at the top of this page pins the label git:20261007.b35fc4b, 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_fr23byceeaczsqwt)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 21, 2026 and Oct 7, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.b35fc4b latest | 2026-10-07 | b35fc4b | 22,580 B | A | view · diff |
| git:20261004.00bb0c5 | 2026-10-04 | 00bb0c5 | 22,543 B | A | view · diff |
| git:20260921.1b27178 | 2026-09-21 | 1b27178 | 22,526 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 (22580 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
tomzx/agents · 12 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fr23byceeaczsqwt GET https://markdownregistry.com/api/v1/resolve?ref=tomzx/agents/propagate-changes GET https://markdownregistry.com/api/v1/blob/0fb3eac612d2e7961363d314762c3d33b1409660ab4beb8248a009f9d9e2bdcb
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.