メニュー
This skill should be used when the user asks to "review page", "stamp as reviewed", "mark reviewed", "review documentation", "add review stamp", "mark page as checked", or mentions wanting to track who has reviewed a documentation page and when.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user asks to "create a tortoise model", "new tortoise project", "tortoise orm", "async orm", "aerich migration", "fastapi tortoise", "tortoise model abstract", "tortoise base class", or mentions Tortoise ORM project structure, model organization, querysets, signals, transactions, or testing. Provides opinionated enterprise patterns: model-per-file, abstract Base interfaces for mocks/transitions, strict class member ordering, FastAPI lifespan, built-in Tortoise migrations (never Aerich), Pydantic v2, pytest.
Use when the user wants to embed an architecture diagram directly inside a React/Vite site as inline SVG (no html2canvas, no external scripts, no separate HTML file). Produces an `arch-diagram` fenced markdown block that the site's React renderer expands — including `<lucide-icon>` placeholders for semantic icons. Companion to the `architecture-diagram` skill, which produces standalone HTML.
Use when the user asks for a system, infrastructure, cloud, security, network topology, or architecture diagram. Produces polished dark-themed self-contained HTML+SVG files with mathematically-correct label placement, clean-background priority, text halos, and leader lines.
Use when the user asks for a mindmap, mind-map, concept map, idea tree, brainstorm diagram, or any radial topic explosion ("draw a mindmap of X", "map out the themes around Y", "mindmap the differentiators of Z"). Produces dark-themed self-contained HTML+SVG with a central root, branches radiating in all directions, halo text, Q-curved Bezier connectors, and geometry-audit gating.
Use when the user asks for a sequence diagram, ladder diagram, message-exchange diagram, or any temporal flow showing who talks to whom in order ("draw the OAuth flow", "show the request lifecycle", "diagram the protocol over time", "sequence diagram for X"). Produces dark-themed self-contained SVG with actor lifelines, sync/async/return messages, self-loops, halo text, and a geometry-audit gate that knows about lifelines.
This skill should be used when the user asks to "create ADR", "document decision", "architecture decision", "add decision record", or mentions needing to record a technical decision with status tracking and category organization.
| name | secondbrain-review |
| description | This skill should be used when the user asks to "review page", "stamp as reviewed", "mark reviewed", "review documentation", "add review stamp", "mark page as checked", or mentions wanting to track who has reviewed a documentation page and when. |
Mark a documentation page as reviewed by appending a {date, name} entry to the reviewed_by list in frontmatter. Multiple reviewers accumulate over time.
/secondbrain-review <page-path> [reviewer]
page-path — path to the markdown file (e.g., docs/guides/setup.md)reviewer — optional full name; defaults to review.default_reviewer from .claude/data/config.yaml, or prompts user if not configuredVerify the project has a .claude/data/config.yaml with a review section:
review:
default_reviewer: "Jane Smith"
thresholds:
fresh_days: 30
aging_days: 90
If the review section is missing, ask the user if they want to add it and configure a default reviewer name.
---
reviewed_by:
- date: 2026-02-13
name: Jane Smith
- date: 2026-02-14
name: John Doe
---
Each review is an entry with date (YYYY-MM-DD) and name (full name). The list grows over time — never remove previous entries.
Extract the page path from the first argument. If a second argument is provided, use it as the reviewer name. Otherwise:
review.default_reviewer from .claude/data/config.yamlnull or missing, check the team section in config for a single member to useRead the target file. Verify it exists and is a markdown file under the docs/ directory.
If the file has reviewed_by as a list — append a new entry with today's date and the reviewer name. Do not add a duplicate if the same person already reviewed on the same date.
If the file has legacy format (reviewed_by: "Name" + last_reviewed: date) — convert to the list format, preserving the existing review as the first entry, then append the new one. Remove the last_reviewed field.
If the file has no reviewed_by — add a reviewed_by list to frontmatter containing one entry. If there is no frontmatter at all, add a frontmatter block.
Show the user the exact changes that will be made (old vs new frontmatter). Wait for explicit user approval before writing.
Apply the frontmatter changes using the Edit tool.
Show a summary:
Reviewed: docs/guides/setup.md
Reviewer: Jane Smith
Date: 2026-03-30
Total reviews: 3
/secondbrain-review docs/guides/setup.md
# Appends: - date: 2026-03-30
# name: Jane Smith (from config default)
/secondbrain-review docs/architecture/overview.md "John Doe"
# Appends: - date: 2026-03-30
# name: John Doe
Adding a second review to an already-reviewed page:
# Before:
reviewed_by:
- date: 2026-01-15
name: Jane Smith
# After /secondbrain-review page.md "John Doe":
reviewed_by:
- date: 2026-01-15
name: Jane Smith
- date: 2026-03-30
name: John Doe
team section exists in config, resolve aliases to full names.ReviewBadge component in the VitePress theme automatically renders review status from the reviewed_by listconfig.yaml under review.thresholds:
fresh_days (default 30) — greenfresh_days to aging_days (default 90) — yellowaging_days — orangereviewed_by: string + last_reviewed) is supported for backwards compatibility/secondbrain-freshness tracks entity record currency