diff-project SKILL.md skillA
diff-project from luiseiman/dotforge is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add luiseiman/dotforge/diff-project@git:20261007.217cdf3Pins git:20261007.217cdf3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- luiseiman/dotforge
- Path
skills/diff-project/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261007.217cdf3, committed Oct 7, 2026
- First version recorded
- Mar 19, 2026
- Size
- 2,648 bytes
- Repository stars
- 8
- License
- MIT
Shows what changed in dotforge since the project's last sync, to decide whether running /forge sync is worthwhile.
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
# Diff Project Show what changed in dotforge since the last synchronization of the current project. ## Step 1: Identify project baseline 1. Read `$DOTFORGE_DIR/registry/projects.local.yml` 2. Find the current project by `path` (compare with `$PWD`) 3. Get `dotforge_version` and `last_sync` 4. If no `dotforge_version` is registered (null), report: ``` Project not synced — no baseline to compare against. Run /forge sync to establish baseline. ``` And stop. ## Step 2: Verify local manifest If `.claude/.forge-manifest.json` exists in the current project: 1. Read it and get the version and file hashes 2. For each file in the manifest, calculate `shasum -a 256 <file> | cut -d' ' -f1` 3. Compare against the registered hash 4. Report locally modified files (hash differs) and deleted files 5. Use the manifest version as baseline (more precise than the registry) If manifest does NOT exist, continue to Step 3 using git log. ## Step 3: Detect changes in dotforge Run in `$DOTFORGE_DIR/`: ```bash git log --oneline v<version>..HEAD -- template/ stacks/ ``` Where `<version>` is the tag corresponding to the project's `dotforge_version`. …
Read the whole file at its exact version.
How to install
mdr add luiseiman/dotforge/diff-project@sha256:5b6c52b4a75a059aThe line at the top of this page pins the label git:20261007.217cdf3, 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_oydo5f625x2se2h5)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 19, 2026 and Oct 7, 2026, about one every 50 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.217cdf3 latest | 2026-10-07 | 217cdf3 | 2,648 B | A | view · diff |
| git:20260405.f2216fd | 2026-04-05 | f2216fd | 2,642 B | A | view · diff |
| git:20260405.f115d49 | 2026-04-05 | f115d49 | 2,666 B | A | view · diff |
| git:20260319.6be3b73 | 2026-03-19 | 6be3b73 | 2,781 B | A | view · diff |
| git:20260319.f882522 | 2026-03-19 | f882522 | 2,823 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 (2648 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
luiseiman/dotforge · 8 stars · license MIT · pushed 2026-10-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oydo5f625x2se2h5 GET https://markdownregistry.com/api/v1/resolve?ref=luiseiman/dotforge/diff-project GET https://markdownregistry.com/api/v1/blob/5b6c52b4a75a059a7af54f9aa4e2de052edd736e23d30013c1d83b28aeb6af2c
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.