Coordinate independent second-pass reviews of internal Markdown documents.
npx skills add https://github.com/lithiumtoast/hearthportal --skill review-lithiumtoast
Please help me install this Agent Skill. Skill: review Source: https://github.com/lithiumtoast/hearthportal/tree/main/.claude/skills/review Command: npx skills add https://github.com/lithiumtoast/hearthportal --skill review-lithiumtoast
Independent, structured reviews of internal documents to surface gaps, risks, and quality issues before publishing or sharing.
Run /review <slug> to start a structured review of the document.
High-intent search queries and answers about installing and using this skill.
Automate document review workflows by running a command that spawns a fresh-context subagent to read markdown files cold and produce a structured verdict. The review outcome is stored as a daily review file while preserving the original document body.
Perform an independent quality assurance check by spawning a fresh-context subagent to evaluate the document unbiased. It surfaces gaps, risks, and quality issues before publishing, storing the structured verdict in a dedicated reviews directory.
A subagent-based review works by spawning a fresh context to read the target markdown document cold, ensuring an unbiased evaluation. It generates a structured verdict file and updates the document's frontmatter status without modifying the original content.
Yes, you can update document frontmatter status automatically during a review. The process reads the target document, evaluates it via a subagent, and updates the frontmatter status when present to reflect the review outcome while preserving the original body.
No, the document review process does not modify the original markdown content. It preserves the original body entirely, only updating the frontmatter status when present and generating a separate structured verdict file in a dedicated reviews directory.
Automated markdown document reviews require files stored under the docs/*/*/*.md path format. The review output is generated and stored at docs/<context>/reviews/<slug>-YYYY-MM-DD.md for traceability.
po4ykaOrganize and triage Markdown task files under docs/tasks/issues.
NSEvteevValidate review.md documents for required frontmatter, sections, verdict, and status.
elasticAudit Elastic documentation markdown frontmatter for required fields and formatting.
mneves75Dispatch a code-reviewer subagent to categorize issues by severity.
