Loading...
Loading...
Found 17 Skills
Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs. Use when asked to run or apply the repo's pre-release audit, validate docs/next before release, inspect issue refs that release CI will close, or finalize release docs for herdr.
Write, edit, review, or audit user-facing documentation for the eve repository. Use for changes under docs/, documentation tied to eve APIs or CLI behavior, docs work based on Slack or support feedback, and requests to make eve docs clearer, more natural, or less AI-patterned while verifying claims against current source, tests, CLI help, public releases, and repository conventions.
Periodically audit a repository's docs for staleness against the implementation: run a cheap mechanical scan (dead source-path references, dead links, leftover DEPRECATED/TBD banners, doc-vs-code freshness gap, git-invisible ignored leftovers, completed-but-undeleted plan files), then dispatch parallel read-only agents to verify only the suspicious docs against source, and finally propose update / delete / migrate-to-ADR dispositions for user approval. Use on a monthly or quarterly docs review, after large refactors or renames, or when asked whether docs are stale.
Create, restructure, review, audit, or migrate DeepSeek Harness Markdown documentation, package READMEs, and the documentation website using audience-first hierarchy, kind-mapped YAML metadata, bilingual line alignment, summary/contents navigation, progressive user-to-developer detail, executed-operation fact-checking, and repository validation. Use for new or revised DSH docs, docs-tree organization, documentation-quality audits and budgets, website page publishing, and bilingual documentation structure changes.
v2.5.0 — Use when bootstrapping, completing, updating, or auditing project documentation, or documenting a feature/module/epic: AGENTS.md + docs/, ADRs, roadmap, docs/features/<slug>/, docs/plans/<slug>/. Triggers: "document this project", "bootstrap docs", "sync docs", "audit docs", "docs vs code", "from zero", "new feature", "nueva feature", "promové el plan", "after ark-check", "arkgate bridge", "knowledge dashboard", /documentation-manager. Intents: integrate, audit, from-zero. Feature autopilot v2; Implementation bridge opt-in; ArkGate post-gate sync; dashboard HTML; polyglot + monorepo hubs; team governance (docs/team); living claims v0 + local CI structural audit (Knowledge OS first increment toward 100×). On conflict code wins.