review-followups SKILL.md skillA
review-followups from phmatray/ai-migration-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add phmatray/ai-migration-kit/review-followups@git:20261010.9485205Pins git:20261010.9485205 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- phmatray/ai-migration-kit
- Path
skills/review-followups/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261010.9485205, committed Oct 10, 2026
- First version recorded
- Aug 31, 2026
- Size
- 9,382 bytes
- Repository stars
- 4
- License
- MIT
Consolide et met à jour les suivis ouverts des migrations (next_steps/deferred des migration/report.json + backlog du kit). Use whenever the user asks what remains open across migrated repos, wants a status of pending decisions, says a follow-up item is done, or decides to close/abandon one — triggers on « fais le point », « qu'est-ce qui reste », « suivis », « c'est fait, coche-le », « on ne le fera pas », "what's still open", "status of the follow-ups", "next steps", "mark it done…
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
# Migration follow-ups — aggregation and updates The pipeline delivers verified apps **and** a queue of follow-ups: decisions that belong to the owner alone, quick tasks, deliberate deferrals. That queue already lives, structured, in each migrated repo's `migration/report.json` (`next_steps`, `deferred`) — this skill surfaces it and updates it **at the source**. Never a parallel list: a separate tracker would diverge from the reports, which are the executive truth and the dashboard's input. Throughout, **`<kit>`** is the plugin root — resolve it as `<skill-dir>/../..`, where `<skill-dir>` is this skill's base directory (given when the skill loads). Kit script paths resolve from there, never from the current working directory. ## Taking stock 1. Determine the repos: those passed as arguments, else the migrated repos known from the conversation/memory, else ask. Add `--backlog <kit>/docs/backlog.md` if the kit repo is accessible (trigger-tagged debts). 2. Run the kit's tool (mandatory — rule 7, never manual aggregation): ```bash python3 "<kit>/scripts/followups.py" <repo1> <repo2> … --backlog "<kit>/docs/backlog.md" ``` …
Read the whole file at its exact version.
How to install
mdr add phmatray/ai-migration-kit/review-followups@sha256:c4c480bdd8904941The line at the top of this page pins the label git:20261010.9485205, 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_tspijcwotmctnsit)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 31, 2026 and Oct 10, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261010.9485205 latest | 2026-10-10 | 9485205 | 9,382 B | A | view · diff |
| git:20260914.a9bc0b6 | 2026-09-14 | a9bc0b6 | 9,406 B | A | view · diff |
| git:20260905.fff03f3 | 2026-09-05 | fff03f3 | 9,416 B | A | view · diff |
| git:20260831.d1e53de | 2026-08-31 | d1e53de | 9,159 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 (9382 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
phmatray/ai-migration-kit · 4 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tspijcwotmctnsit GET https://markdownregistry.com/api/v1/resolve?ref=phmatray/ai-migration-kit/review-followups GET https://markdownregistry.com/api/v1/blob/c4c480bdd89049416222536957398c56bb13df5c23fd72797354984774af17db
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 phmatray/ai-migration-kit
Every file in phmatray/ai-migration-kit