flow-next-impl-review SKILL.md skillA
flow-next-impl-review from gmickel/flow-next is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gmickel/flow-next/flow-next-impl-review@git:20261031.3796bc0Pins git:20261031.3796bc0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gmickel/flow-next
- Path
plugins/flow-next/codex/skills/flow-next-impl-review/SKILL.md- Versions recorded
- 14
- Latest version
- git:20261031.3796bc0, committed Oct 31, 2026
- First version recorded
- Aug 13, 2026
- Size
- 7,859 bytes
- Repository stars
- 718
- License
- MIT
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
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
# Implementation review
You coordinate; the configured backend reviews. Never author a verdict yourself, and use one
backend for the whole review. Read [working-rules.md](../../references/working-rules.md) first:
its Review section decides which findings you fix.
Arguments: `[task id] [--base <commit>] [--review=<backend>] [--deep[=passes]]
[--validate] [--interactive] [--no-triage] [focus areas]`. Without `--base` the whole branch is
reviewed against main. A spec or branch review passes no id.
## 1. Setup
One Bash call; fill the three literals from the arguments.
```bash
set -e
FLOWCTL="${CODEX_HOME:-$HOME/.codex}/scripts/flowctl"
[ -x "$FLOWCTL" ] || FLOWCTL="<plugin-root>/scripts/flowctl" # <plugin-root> = the directory two levels above this skill's SKILL.md file (the harness gave you that file's absolute path when the skill loaded); substitute it literally
[ -x "$FLOWCTL" ] || FLOWCTL=".flow/bin/flowctl"
REVIEW_ID="<task id, or empty for a spec or branch review>"
BACKEND="<value of --review, or empty>"
DIFF_BASE="<value of --base, or empty>"
[ -n "$BACKEND" ] || BACKEND=$("$FLOWCTL" review-backend "$REVIEW_ID")
…Read the whole file at its exact version.
How to install
mdr add gmickel/flow-next/flow-next-impl-review@sha256:17a48dd4d107b3c8The line at the top of this page pins the label git:20261031.3796bc0, 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_sjgsj72hs5tbsa5h)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 14 versions of this file, between Aug 13, 2026 and Oct 31, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261031.3796bc0 latest | 2026-10-31 | 3796bc0 | 7,859 B | A | view · diff |
| git:20261010.d5660ce | 2026-10-10 | d5660ce | 8,059 B | A | view · diff |
| git:20261005.03ae8e1 | 2026-10-05 | 03ae8e1 | 7,993 B | A | view · diff |
| git:20261004.c5b2b00 | 2026-10-04 | c5b2b00 | 7,866 B | A | view · diff |
| git:20261004.6102845 | 2026-10-04 | 6102845 | 7,949 B | A | view · diff |
| git:20261004.e06ddc0 | 2026-10-04 | e06ddc0 | 7,472 B | A | view · diff |
| git:20261002.af27800 | 2026-10-02 | af27800 | 7,364 B | A | view · diff |
| git:20260926.b4c980a | 2026-09-26 | b4c980a | 18,116 B | A | view · diff |
| git:20260911.f92da65 | 2026-09-11 | f92da65 | 17,996 B | A | view · diff |
| git:20260905.cfc29f1 | 2026-09-05 | cfc29f1 | 18,107 B | A | view · diff |
| git:20260904.6f7990d | 2026-09-04 | 6f7990d | 17,863 B | A | view · diff |
| git:20260902.7bf525d | 2026-09-02 | 7bf525d | 17,876 B | A | view · diff |
| git:20260827.cd9664b | 2026-08-27 | cd9664b | 16,298 B | A | view · diff |
| git:20260813.fe6544b | 2026-08-13 | fe6544b | 16,137 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 (7859 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
gmickel/flow-next · 718 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_sjgsj72hs5tbsa5h GET https://markdownregistry.com/api/v1/resolve?ref=gmickel/flow-next/flow-next-impl-review GET https://markdownregistry.com/api/v1/blob/17a48dd4d107b3c835ec5b55de89b40bc8e6692fcb521cd0a5b42c8529e54b23
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 gmickel/flow-next
Every file in gmickel/flow-next