dekko-review-context SKILL.md skillA
dekko-review-context from aahlijia/dekko is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add aahlijia/dekko/dekko-review-context@git:20260927.bab3b36Pins git:20260927.bab3b36 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- aahlijia/dekko
- Path
integrations/claude/skills/dekko-review-context/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260927.bab3b36, committed Sep 27, 2026
- First version recorded
- Aug 21, 2026
- Size
- 3,691 bytes
- Repository stars
- 6
- License
- MIT
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 (`/code-review`, `/review`, or an equivalent) against a diff in a repo with a `.dekko/` directory.
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
# 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@sha256:b047af8f1515826aThe line at the top of this page pins the label git:20260927.bab3b36, 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_d7pnq6ekwyrlajly)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 21, 2026 and Sep 27, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260927.bab3b36 latest | 2026-09-27 | bab3b36 | 3,691 B | A | view · diff |
| git:20260925.f43cf39 | 2026-09-25 | f43cf39 | 4,160 B | A | view · diff |
| git:20260922.4966520 | 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 (3691 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 · 6 stars · license MIT · pushed 2026-10-15 · 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/b047af8f1515826a917984e142ac8db81d9560c50bac3c71a06199c97a518f53
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.