daily-code-review SKILL.md skillA
daily-code-review from flagrare/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add flagrare/agent-skills/daily-code-review@git:20261008.b2c58b8Pins git:20261008.b2c58b8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- flagrare/agent-skills
- Path
plugins/flagrare/skills/daily-code-review/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261008.b2c58b8, committed Oct 8, 2026
- First version recorded
- May 26, 2026
- Size
- 8,612 bytes
- Repository stars
- 12
- License
- none declared
Generate a daily code review report showing stale PRs, items needing your attention, and active work for your team. Use whenever the user asks for a PR report, code review status, daily standup prep, team PR overview, "what needs review", "what's stale", "show me open PRs", "daily review", "PR check", "review report", "what should I look at today", or any question about tracking pull request activity across a team or pod. Also trigger when the user mentions a specific pod name that matches a…
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
# Daily Code Review Report
> **No em-dashes.** Nothing this skill writes may contain an em-dash; use a comma, colon, or parentheses instead. Enforced by a repo hook that flags em-dashes in generated `.md`. See `/flagrare:write-docs`.
Generate a team-wide pull request status report focused on actionable next steps. The report surfaces stale PRs, items needing the runner's personal attention, and a quick FYI on active work, so the reader knows exactly what to do when they open GitHub.
## Setup (first run only)
Team configs live at **`~/.claude/skills/flagrare/daily-code-review/teams/*.json`**: one file per team, outside the plugin tree so they survive plugin updates and reinstalls.
In Bash, expand `~` explicitly: `"$HOME/.claude/skills/flagrare/daily-code-review/teams"`. The directory may not exist yet, `mkdir -p "$HOME/.claude/skills/flagrare/daily-code-review/teams"` before writing.
### Step 1: Migrate legacy configs (one-time)
If the new dir has no team files but the legacy per-plugin dir does, migrate them:
```bash
LEGACY="{skill_directory}/teams" # old location, lost on plugin reinstall
NEW="$HOME/.claude/skills/flagrare/daily-code-review/teams"
…Read the whole file at its exact version.
How to install
mdr add flagrare/agent-skills/daily-code-review@sha256:3ad95f4892c7bed7The line at the top of this page pins the label git:20261008.b2c58b8, 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_ly5tlu7htwmvqqju)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 26, 2026 and Oct 8, 2026, about one every 45 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261008.b2c58b8 latest | 2026-10-08 | b2c58b8 | 8,612 B | A | view · diff |
| git:20260611.9c42181 | 2026-06-11 | 9c42181 | 8,433 B | A | view · diff |
| git:20260604.baf03a8 | 2026-06-04 | baf03a8 | 8,297 B | A | view · diff |
| git:20260526.248a37e | 2026-05-26 | 248a37e | 7,231 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 (8612 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
flagrare/agent-skills · 12 stars · license none declared · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ly5tlu7htwmvqqju GET https://markdownregistry.com/api/v1/resolve?ref=flagrare/agent-skills/daily-code-review GET https://markdownregistry.com/api/v1/blob/3ad95f4892c7bed71a97d05d6048fe2c499670b8c9e7f9e702f8a0bd4f752353
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.