agentsclimarketplace

Docs drift maintenance

Skill chf3198/megingjord-harness/skills/docs-drift-maintenance

AI agent governance harness: baton workflow, fleet LLM routing (Ollama/Claude/OpenRouter), and CI gates for Copilot, Claude Code, and Codex.

Install
npx -y skills add chf3198/megingjord-harness --skill docs-drift-maintenance

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Detect and remediate documentation drift after code, config, workflow, or UX changes. Use after implementation, before merge, and before release.

SKILL.md

2.8 KB, as published. Nobody here has run it

Docs Drift Maintenance

When to use

  • After any change to commands, config, workflows, API/CLI behavior, or release process.
  • Before merge/release if docs accuracy is part of acceptance.
  • Before declaring a feature complete (not just gates-complete).

Documentation coverage matrix (required)

For feature-adds and behavior changes, evaluate all applicable surfaces:

  1. Local operator docs
    • README.md
    • docs/technical/system-stability.md
    • docs/workflow/learnings.md
  2. Public repository docs
    • .github/CONTRIBUTING.md
    • .github/PULL_REQUEST_TEMPLATE.md
    • community profile files (CODE_OF_CONDUCT.md, SECURITY.md, SUPPORT.md) when behavior changes affect contributor workflow
  3. VS Code extension public profile
    • vscode-extension/README.md
    • vscode-extension/CHANGELOG.md
    • vscode-extension/package.json metadata/settings descriptions
  4. Release traceability docs
    • root CHANGELOG.md
    • release notes / GitHub release object
  5. Inline code documentation (added #101 — global linting governance)
    • JS/TS: JSDoc on all exported/public functions (@param, @returns, @description)
    • Python: Google-style docstrings on all public functions, classes, and modules
    • Bash: Header comment block on each script; inline comments on non-obvious logic
    • CSS: Section header comments; non-obvious rule explanations
    • Governed by lint-configs/eslint.config.devenv.js (JSDoc rules) and lint-configs/ruff.devenv.toml (D rules)
    • Drift check: run npm run lint:all; any new jsdoc/* or D* violations are inline-doc drift

Procedure

  1. Enumerate changed behavior/config/workflow/code surfaces.
  2. Map each change to impacted docs using the coverage matrix above.
  3. Identify stale, missing, or contradictory statements.
  4. Apply minimal doc deltas that restore correctness and traceability.
  5. Verify docs now match actual behavior and invocation paths.
  6. Record what was intentionally N/A and why.

Output format

  • drift_status: none|found|critical
  • impacted_docs: file list with reason
  • required_updates: concrete edits required
  • verification_checks: objective checks confirming alignment
  • evidence: code/workflow changes correlated to docs updates
  • not_applicable: surfaces reviewed but intentionally N/A

Standards

  • Docs updates must ship with behavior/config/workflow changes.
  • Keep wording precise, testable, and user-actionable.
  • Avoid speculative claims unsupported by current implementation.
  • "All tests pass" does not imply docs are complete.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.