From secondbrain
Stamps Markdown documentation pages as reviewed by appending {date, reviewer} entries to frontmatter. Tracks multiple reviews over time; uses .claude config defaults and shows diffs for approval.
npx claudepluginhub sergio-bershadsky/ai --plugin secondbrainThis skill uses the workspace's default tool permissions.
Mark a documentation page as reviewed by appending a `{date, name}` entry to the `reviewed_by` list in frontmatter. Multiple reviewers accumulate over time.
Creates, shares, views, comments on, edits, and runs human-in-the-loop reviews of markdown documents via Proof editor at proofeditor.ai. Use for collaborative iteration on specs, plans, drafts with local file sync.
Launches interactive web UI for reviewing markdown content from files, plans, or conversation using checkboxes and comments.
Audits documentation staleness via git history and maintains quality with auto-fixes. Maps code paths to docs in $JAAN_DOCS_DIR. Use for reviewing or updating docs.
Share bugs, ideas, or general feedback.
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