Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

docs-review

Estrelas1

Forks0

Atualizado8 de junho de 2026 às 23:25

Documentation review for the Mycelium corpus. Checks that cross-references resolve, notation is normalized, grounding labels are valid, ADR/RFC/DN status transitions are legal and append-only, and the changelog reflects the change. Most of this repo is normative docs, so this is the primary review for a docs-only diff.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

tzervas

tzervas/mycelium

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	docs-review
description	Documentation review for the Mycelium corpus. Checks that cross-references resolve, notation is normalized, grounding labels are valid, ADR/RFC/DN status transitions are legal and append-only, and the changelog reflects the change. Most of this repo is normative docs, so this is the primary review for a docs-only diff.
when_to_use	Use when reviewing changes to docs/, research/, READMEs, RFCs/ADRs/notes, or any markdown; or when asked to check documentation correctness/consistency before merge.
argument-hint	[PR#\|<base>...<head>\|<commit>\|<path>] [--tier T0\|T1\|T2] [--all]
allowed-tools	Bash(git diff:), Bash(git show:), Bash(git log:), Bash(just links:), Bash(git grep:*), Read, Grep, Glob

docs-review

Documentation review, repo-grounded. Shared triage/severity/report contract: review-rubric — read it first, pick a tier, emit the report. A docs-only diff is still reviewed properly (correctness, grounding, consistency) even though its security tier is light.

Checklist

References & structure

Every relative link / cross-reference / @import resolves (run/trust just links — the offline checker). A moved or renamed file must leave no dangling reference (prose, backticked paths, and tables included — the link checker won't catch backticked paths, so grep them: git grep -n "old/path").
Section/ID references are real: RFC-000x §y, FR/NFR/VR/SC/KC ids, ADR numbers, survey/ research labels. A reference to a non-existent section/id → High.
Doc index (docs/Doc-Index.md) and the dependency DAG stay consistent with what exists. Files marked forthcoming (e.g. docs/planning/) are fine as long as they're labeled so.

Notation & house style

Guarantee lattice renders as Exact ⊐ Proven ⊐ Empirical ⊐ Declared (the ⊐ form, not ⊃); implication ⟹; unicode superscripts (µ²). Flag notation drift (Medium).
Markdown matches .markdownlint.jsonc (run/trust just md). Emphasis style consistent.

Grounding & honesty (CONTRIBUTING)

Every normative claim cites its basis (G1–G11, tensions A–E, R1–R8, T0.x–T2.x) or is explicitly an open question. An ungrounded assertion stated as fact → High.
Guarantee/bound language stays honest per VR-5 (per-model/op, never aggregate); a Proven claim names the theorem + checked side-conditions. Hallucinated citations → Critical.

Decision discipline (append-only)

Status moves forward only (Draft/Proposed/Preliminary → Accepted → Superseded; notes → Resolved). An Accepted decision edited in place (beyond editorial/status) → Critical; it must be superseded with a forward link instead.
The doc's own changelog footer and the top-level CHANGELOG.md record the change (defer the edit to the changelog skill). A status transition with no changelog entry → Medium.

Hallucination pass

Verify each new factual claim against its cited source file/section. Numbers, dates, names, and IDs must be real. Cross-check that the diff's stated intent matches what it actually changes.

Report

Emit the rubric §4 format, advisory posture: file:line → what → why → fix, then summary, analysis, and prioritized recommendations (always in --all mode).

Mais deste repositório

mesmo repositório

gen-book

tzervas/mycelium

Generate the validated "read" (prose) that accompanies extracted code facts — language-book chapters, reference-manual entries, and learning-corpus lessons — from the committed index JSON, with a mandatory faithfulness gate so nothing is hallucinated. Wraps tools/llm-harness/narrate/ (Generator -> FaithfulnessChecker -> Loop): only validated, cited prose is committed; the rest is dropped and reported (never silently). Deterministic Mock backends by default (offline/CI).

2026-07-111

native-translate

tzervas/mycelium

Classify a Rust construct's Mycelium native-translation strategy using the ratified DN-111 native-equivalence taxonomy — Native Equivalent · Idiomatic Remapping · Approximation · Interop Bridge (DN-110's Adaptation/Solution/Approximation/Bridge handles are permanent aliases). Runs DN-110 §9's six-step decision procedure: verify-first against the corpus, identify the underlying PROBLEM (not Rust's mechanism), classify by the {exact?}×{native?} generator, apply the DN-109 §3.2 auto-fire ratchet, and emit a register-style record with an honest, never-upgraded guarantee tag (VR-5).

2026-07-111

issues-sync

tzervas/mycelium

Reconcile the repo's GitHub issues to the committed source of truth (tools/github/issues.yaml + idmap.tsv) the rate-limit-frugal, diff-based way: one bulk snapshot, only-the-deltas writes, dry-run by default. Hits the API only for issues that are missing (create) or drifted (update), skipping everything already in sync. A periodic DESKTOP operation (real API) — not for the cloud/web session.

2026-07-101

changelog

tzervas/mycelium

Maintain Mycelium's changelogs. Keeps the top-level CHANGELOG.md (Keep a Changelog 1.1.0, ISO dates, design-phase framing) and each doc's changelog footer in sync with a change, and enforces the append-only status discipline (Draft→Accepted→Superseded, Resolved for notes). Use when finishing a change, moving a doc's status, or cutting a release.

2026-07-091

forward

tzervas/mycelium

Develop a change forward (up the tiers) the spec-first, staged, context-windowed way: spec/DN (requirements, DoD, user stories) -> public API -> private API -> component seam-map -> code, each stage a bounded working set that persists a compact artifact and drops from context once consumed (DN-96). Owns the staged design pipeline, the change-sizing check (soft ~1-2k / hard 4,000 LOC), and the precursor doc/index-branch mechanic; delegates isolation, review+merge-up, index regen, and the main landing to /worktree-guard, /pr-land, /doc-index + /tero-refresh, and /land, following DN-97's ratified Rank-1 batch-engine command sequences for the actual landing.

2026-07-091

sync-down

tzervas/mycelium

Propagate a squashed landing on `main` back down to the persistent lower trunks -- main -> integration -> dev -- via a plain, no-force merge per tier (DN-97 Rank 1, maintainer-ratified: same-content trunks make this trivially conflict-free -- no merge-driver, no veto, no keep-list). Landed through the same PR-merge mechanism /pr-land and /land already use for these protected branches, never a raw git push. Run once per batch after 1-6 disjoint work-set squashes land on main. Also covers the in-flight-adapt one-liner for a still-open work-set branch.

2026-07-091

name	docs-review
description	Documentation review for the Mycelium corpus. Checks that cross-references resolve, notation is normalized, grounding labels are valid, ADR/RFC/DN status transitions are legal and append-only, and the changelog reflects the change. Most of this repo is normative docs, so this is the primary review for a docs-only diff.
when_to_use	Use when reviewing changes to docs/, research/, READMEs, RFCs/ADRs/notes, or any markdown; or when asked to check documentation correctness/consistency before merge.
argument-hint	[PR#\|<base>...<head>\|<commit>\|<path>] [--tier T0\|T1\|T2] [--all]
allowed-tools	Bash(git diff:), Bash(git show:), Bash(git log:), Bash(just links:), Bash(git grep:*), Read, Grep, Glob

docs-review

Checklist

References & structure

Every relative link / cross-reference / @import resolves (run/trust just links — the offline checker). A moved or renamed file must leave no dangling reference (prose, backticked paths, and tables included — the link checker won't catch backticked paths, so grep them: git grep -n "old/path").
Section/ID references are real: RFC-000x §y, FR/NFR/VR/SC/KC ids, ADR numbers, survey/ research labels. A reference to a non-existent section/id → High.
Doc index (docs/Doc-Index.md) and the dependency DAG stay consistent with what exists. Files marked forthcoming (e.g. docs/planning/) are fine as long as they're labeled so.

Notation & house style

Guarantee lattice renders as Exact ⊐ Proven ⊐ Empirical ⊐ Declared (the ⊐ form, not ⊃); implication ⟹; unicode superscripts (µ²). Flag notation drift (Medium).
Markdown matches .markdownlint.jsonc (run/trust just md). Emphasis style consistent.

Grounding & honesty (CONTRIBUTING)

Every normative claim cites its basis (G1–G11, tensions A–E, R1–R8, T0.x–T2.x) or is explicitly an open question. An ungrounded assertion stated as fact → High.
Guarantee/bound language stays honest per VR-5 (per-model/op, never aggregate); a Proven claim names the theorem + checked side-conditions. Hallucinated citations → Critical.

Decision discipline (append-only)

Status moves forward only (Draft/Proposed/Preliminary → Accepted → Superseded; notes → Resolved). An Accepted decision edited in place (beyond editorial/status) → Critical; it must be superseded with a forward link instead.
The doc's own changelog footer and the top-level CHANGELOG.md record the change (defer the edit to the changelog skill). A status transition with no changelog entry → Medium.

Hallucination pass

Verify each new factual claim against its cited source file/section. Numbers, dates, names, and IDs must be real. Cross-check that the diff's stated intent matches what it actually changes.

Report

Emit the rubric §4 format, advisory posture: file:line → what → why → fix, then summary, analysis, and prioritized recommendations (always in --all mode).