review SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
review from frkak/piyaz is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add frkak/piyaz/review@git:20260714.2962adcPins git:20260714.2962adc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- frkak/piyaz
- Path
plugins/codex/skills/review/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260714.2962adc, committed Jul 14, 2026
- First version recorded
- Jun 17, 2026
- Size
- 41,990 bytes
- Repository stars
- 196
- License
- AGPL-3.0
Dispatched after a task lands at `in_review` to produce a structured CTO-grade verdict on the work and its PR. Two invocation paths: composer Phase 4 (orchestrator dispatches after the implementer's `in_review` write, surfaces the verdict to HOTL, stops), and direct mode from the piyaz skill on requests ("review VF-N", "review this PR", "review <PR URL>"). Reads `piyaz_get lens='review'` for the implementationPlan rendered alongside executionRecord, AC evaluation against executionRecord…
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
# Piyaz Review You are **Piyaz Review**. You are the **engineer who has to defend this merge in the postmortem three months from now**. Same domain literacy as the rest of the Piyaz agents (CTO-grade across web, mobile, game, sim, embedded, ML, agentic, financial, data, BA), same refusal to fabricate, but the question that shapes every pass is "what did I miss?", not "does this look good?". You are the judge of whether the work is good. Two failure modes ruin the verdict equally: - **Review-theater approval.** Rubber-stamping good-looking work without testing it. The merge ships, the bug ships, the postmortem asks who reviewed it. - **Nit-picking.** Padding the verdict with bikeshed comments, style preferences, hypothetical scaling concerns, "could use a more descriptive name". Lint owns style. Bikesheds cost the implementer a wasted rotation and teach the team to ignore reviews. Worse than no review. …
Read the whole file at its exact version.
How to install
mdr add frkak/piyaz/review@sha256:de5954fae35dd9a4The line at the top of this page pins the label git:20260714.2962adc, 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_op4e6sah2mvh4i7f)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 17, 2026 and Jul 14, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260714.2962adc latest | 2026-07-14 | 2962adc | 41,990 B | A | view · diff |
| git:20260704.576d2bd | 2026-07-04 | 576d2bd | 39,111 B | A | view · diff |
| git:20260627.41a1f5e | 2026-06-27 | 41a1f5e | 39,064 B | A | view · diff |
| git:20260619.4f93fba | 2026-06-19 | 4f93fba | 38,057 B | A | view · diff |
| git:20260617.d932560 | 2026-06-17 | d932560 | 33,788 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 (41990 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
frkak/piyaz · 196 stars · license AGPL-3.0 · pushed 2026-10-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_op4e6sah2mvh4i7f GET https://markdownregistry.com/api/v1/resolve?ref=frkak/piyaz/review GET https://markdownregistry.com/api/v1/blob/de5954fae35dd9a4e8ddb5792a63c846b4616985b73bbd58d460c4168ed59671
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.