ase-repo-review SKILL.md skillA
ase-repo-review from rse/ase is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rse/ase/ase-repo-review@git:20261019.df1b466Pins git:20261019.df1b466 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rse/ase
- Path
plugin/skills/ase-repo-review/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261019.df1b466, committed Oct 19, 2026
- First version recorded
- Sep 29, 2026
- Size
- 17,037 bytes
- Repository stars
- 62
- License
- Apache-2.0
Perform a holistic, human-reviewer-style critique of the currently staged Git changes (or, with `--unstaged`, of the unstaged and untracked changes, with `--branch`, of a branch against its base, or, with `--commit`, of a single commit) and emit an approve/reject verdict with prioritized, severity-tagged, line-cited findings. Use when the user wants the staged diff, a branch, or a commit "reviewed", "critiqued", or "code-reviewed".
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
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
<purpose name="ase-repo-review">
Review Changes
</purpose>
<expand name="getopt"
arg1="ase-repo-review"
arg2="--severity|-S=(AUTO|LOW|MEDIUM|HIGH) --thorough|-t --staged --unstaged --branch|-b= --commit|-c=">
$ARGUMENTS
</expand>
<objective>
Review the currently staged (and/or unstaged) Git changes, the changes
of a branch against its base, or a single commit the way an
*experienced human reviewer* would - judging them *holistically* against
the change's *own intent* and against *correctness*, *design fit*,
*clarity*, *robustness*, *propagation*, freedom of *residue*, and
*project-convention conformance* - and emit a single *approve /
request-changes verdict* backed by *prioritized*, *severity-tagged*,
*line-cited* findings. This is a *synthesizing critique*, not a mechanical
scan: it complements `ase-code-lint` (mechanical quality), `ase-code-analyze`
(logic/semantics), and `ase-repo-diff` (intent narrative and risk).
</objective>
Procedure
---------
<flow>
1. <step id="STEP 1: Determine Change Set">
…Read the whole file at its exact version.
How to install
mdr add rse/ase/ase-repo-review@sha256:c705537152f7e06eThe line at the top of this page pins the label git:20261019.df1b466, 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_4nqnwj5lhkzkqft3)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 29, 2026 and Oct 19, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.df1b466 latest | 2026-10-19 | df1b466 | 17,037 B | A | view · diff |
| git:20261017.19ede76 | 2026-10-17 | 19ede76 | 16,874 B | A | view · diff |
| git:20261013.9ef8108 | 2026-10-13 | 9ef8108 | 16,878 B | A | view · diff |
| git:20261006.01e8205 | 2026-10-06 | 01e8205 | 15,451 B | A | view · diff |
| git:20260929.9b9ee44 | 2026-09-29 | 9b9ee44 | 8,094 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 (17037 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
rse/ase · 62 stars · license Apache-2.0 · pushed 2026-11-04 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_4nqnwj5lhkzkqft3 GET https://markdownregistry.com/api/v1/resolve?ref=rse/ase/ase-repo-review GET https://markdownregistry.com/api/v1/blob/c705537152f7e06e7d9c37fef4fc6ea3c68fd148fb517d52ef564fc1982aed29
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.