change-impact-check skillA
change-impact-check is agent-read markdown (skill) from yeaight7/agent-powerups: Use before submitting a PR or considering a task done to evaluate the blast radius of your changes -- you touched a public signature, a shared utility, a schema, or added config and need to know what else is affected..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## Purpose Code changes rarely exist in isolation. Before declaring success, evaluate the downstream consequences of your work: what depends on what you changed, and whether those dependents still hold. ## When to Use - Before submitting a PR or marking a task complete - You changed a public method signature, REST endpoint, or database schema - You modified a shared utility, core helper, or widely-imported module - You added or renamed an environment variable or config key ## Inputs - The diff of your changes (staged or committed) - Access to the repository to search for callers and run tests ## Workflow 1. **Scope the diff.** List what actually changed and which files are touched, so you know where to look for fallout. ```bash git diff --stat # files changed + churn size git diff --name-only # bare list to feed into searches ``` 2. **API surface.** If you changed a public method signature, REST endpoint, or database schema, search the entire repository for usages of the old signature. Every caller is a potential break. ```bash git grep -n "oldFunctionName" # all references, with line numbers …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/change-impact-check@git:20260606.bb52817mdr add yeaight7/agent-powerups/change-impact-check@sha256:be9275eafc01b3f8Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_y3iqvouky5ifl3ri)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.bb52817 latest | 2026-06-06 | bb52817 | 3,585 B | A | view · diff |
| git:20260602.c712951 | 2026-06-02 | c712951 | 960 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 (3585 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
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_y3iqvouky5ifl3ri GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/change-impact-check GET https://markdownregistry.com/api/v1/blob/be9275eafc01b3f8718c8640031e080cf07fbcdf84eeb442fd8230a48e7151b0
Your agent 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.
More from yeaight7/agent-powerups
Every file in yeaight7/agent-powerups