dekko-review-context skillA
dekko-review-context is agent-read markdown (skill) from aahlijia/dekko: Give a code-review or PR-description flow a structural head start before reading a diff line by line. Trigger when the user asks for a PR description, a pre-merge summary, or invokes a code-review flow (this repo's `open-agent-hub:review`/`/review`, or an equivalent in another environment) against a diff in a repo with a `.dekko/` directory..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Structural context before reviewing a diff A reviewing agent that reads a diff cold misses what a call graph already knows: what else calls the changed code, what tests should run, and where dekko's own resolver is unsure. `workset`, `impacted_tests`, and `check_ambiguous` already answer these — this skill composes them into review context, run *before* the diff itself, so the read is top-down (structure first, then lines) instead of bottom-up. ## Procedure | Need | Use | |---|---| | What changed and what calls it | `mcp__dekko__workset [rev]` (or `dekko workset [REV]`) | | What tests should run | `mcp__dekko__impacted_tests [rev]` (or `dekko affected [REV]`) | | Where the resolver itself is unsure | `mcp__dekko__check_ambiguous` (or `dekko ambiguous`) | | Just the changed-symbol list with callers, no outlines | `dekko diff [REV]` (CLI only) | 1. **Determine the diff scope.** A git rev range, or the same default `workset`/`impacted_tests` already use: the commit the map was generated at, else `HEAD`. Don't ask the user to specify this unless the default is ambiguous for the request. 2. **Call `workset [rev]`.** Bundles touched-file outlines plus …
Read the whole file at its exact version.
How to install
mdr add aahlijia/dekko/dekko-review-context@git:20260922.4966520mdr add aahlijia/dekko/dekko-review-context@sha256:34314fe85456b7a9Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_d7pnq6ekwyrlajly)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.4966520 latest | 2026-09-22 | 4966520 | 3,957 B | A | view · diff |
| git:20260821.050a9ce | 2026-08-21 | 050a9ce | 3,511 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 (3957 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
aahlijia/dekko · 5 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_d7pnq6ekwyrlajly GET https://markdownregistry.com/api/v1/resolve?ref=aahlijia/dekko/dekko-review-context GET https://markdownregistry.com/api/v1/blob/34314fe85456b7a91cf327a7e3e35e349c60650f902b9c3b54a4949538588794
Your agent 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.