AgentSkillsCN

doc-gardener

维护Sage文档的质量与可读性。在新增、移动、删除或编辑docs/目录下的文档时,或在更新文档索引、修复本地链接失效或陈旧问题、解决文档检查失败时,可使用此功能。

SKILL.md
--- frontmatter
name: doc-gardener
description: Maintain Sage documentation quality and navigability. Use when adding, moving, deleting, or editing docs under docs/, updating docs indexes, or fixing broken/stale local links and docs check failures.

doc-gardener

Objective

Keep docs minimal, accurate, and mechanically checkable.

Workflow

  1. Identify changed docs scope (docs/index.md, docs/agentic/index.md, related pages).
  2. Update links and indexes so every referenced local path resolves.
  3. Keep edits minimal and factual; remove stale references when deleting docs.
  4. Run npm run docs:check.
  5. Run npm run fmt.
  6. Run npm run check when docs changes affect governance or verification scripts.

Standards

  • Keep one canonical entrypoint per audience:
    • User docs: docs/index.md
    • Agent docs: docs/agentic/AGENT-START.md and docs/agentic/index.md
  • Prefer relative local links for repository docs.
  • Avoid unresolved placeholder markers unless tracked intentionally.
  • If work is deferred, log it in the repository issue tracker.

Guardrails

  • Do not change product behavior through docs-only work.
  • Do not add large new doc systems unless requested.
  • Preserve existing repository conventions and wording style.

Output Contract

  • Report files changed, links fixed/removed, and verification commands run.
  • Explicitly call out any deferred docs follow-up entries added.