impact SKILL.md skillB
impact from sysevol-ai/codenib is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sysevol-ai/codenib/impact@git:20261116.1ab51d6Pins git:20261116.1ab51d6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sysevol-ai/codenib
- Path
plugins/codenib/skills/impact/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261116.1ab51d6, committed Nov 16, 2026
- First version recorded
- Nov 9, 2026
- Size
- 1,197 bytes
- Repository stars
- 95
- License
- Apache-2.0
List the tests that the current, uncommitted change can reach, with the call path to each, before finishing a change in a Python repository. Use when asked which tests to run, what a change might break, or to check a change before committing.
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
Find the tests a change can reach, run them, and report what you ran. 1. Run `codenib guard check` in the repository root. It compares the working tree with `HEAD`; pass `--base <revision>` for another starting point. It prints each reachable test with the call path from the test to the changed code, and the tests the change itself rewrote come first. 2. Run the listed tests with the project's own test command. For a test the change rewrote, also run it as it was at the base revision, as the report shows, so that a weakened test cannot hide a regression. 3. Report which tests you ran and their results. A test the report did not list can still fail: the check follows static references and does not see dynamic dispatch or code outside the index. This check is a preview and supports Python only. If `codenib` is missing, tell the user to run CodeNib's `setup` skill (`/codenib:setup` in Claude Code).
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_jambzkwpbh6kj7ih/67affb7739b6bbb4b8e643470af209d8c7b64953dbf9c9696ee5a0f74654d982.json
Then /plugin install impact@markdownregistry-jambzkwpbh6kj7ih in Claude Code. It installs git:20261116.1ab51d6, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add sysevol-ai/codenib/impact@sha256:67affb7739b6bbb4The line at the top of this page pins the label git:20261116.1ab51d6, 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_jambzkwpbh6kj7ih)
4 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in sysevol-ai/codenib/impact since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of impact from somewhere else? Ask it: where did my impact come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Nov 9, 2026 and Nov 16, 2026, about one every 7 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261116.1ab51d6 latest | 2026-11-16 | 1ab51d6 | 1,197 B | B | view · diff |
| git:20261109.9a49727 | 2026-11-09 | 9a49727 | 1,156 B | B | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/impact/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1197 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
sysevol-ai/codenib · 95 stars · license Apache-2.0 · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jambzkwpbh6kj7ih GET https://markdownregistry.com/api/v1/resolve?ref=sysevol-ai/codenib/impact GET https://markdownregistry.com/api/v1/blob/67affb7739b6bbb4b8e643470af209d8c7b64953dbf9c9696ee5a0f74654d982
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 sysevol-ai/codenib
Every file in sysevol-ai/codenib