agentsclimarketplace

Update docs

Skill amurshak/hephaestus/.agents/skills/update-docs

Update documentation to reflect recent work. Use for /update-docs requests.From its SKILL.md

Install
npx -y skills add amurshak/hephaestus --skill update-docs

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

One thing to look at

  • 1 stars1 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.

SKILL.md

2.4 KB, as published. Nobody here has run it

<!-- requires: none --> <!-- chains: none --> <!-- generated from .ai/workflows/update-docs.md; do not edit directly -->

Codex: this skill is the /update-docs adapter. Use Codex role agents from .codex/agents/ when the runtime exposes them; otherwise perform the work directly and keep the same structured output.

Update documentation to reflect recent work.

Steps:

  1. Review recent changes: Run git log --oneline -5 and git diff HEAD~5..HEAD --name-only to understand what was built.

  2. Update CLAUDE.md (project root):

    • Add any new architecture decisions, patterns, or constraints discovered during the work
    • Remove patterns that are now obsolete
    • Keep CLAUDE.md under ~300 lines — trim verbose sections if needed
  3. Record changelog entries:

    • If changelog.d/ exists, write one fragment per change: changelog.d/<issue-or-slug>.<added|changed|fixed|removed>.md, containing the entry body without the leading - . Never edit CHANGELOG.md directly — it is assembled at release by scripts/collect-changelog.sh <version>.
    • Otherwise update CHANGELOG.md (create it with a # Changelog title and ## Unreleased section if the project has none):
      ## Unreleased
      ### Added / Changed / Fixed
      - <concise description of what shipped>
      
      Use ### for category headings — one per category, do not duplicate.
    • Reference issue/PR numbers where applicable
  4. Update README.md only if a public-facing feature or API changed (new endpoint, new CLI command, changed env var).

  5. Run the repo's doc-drift verifiers — scripts that opt in by carrying a # hephaestus:doc-verifier marker, so a project's unrelated tests/check_*.sh is never executed here:

    vs=$(grep -l '# hephaestus:doc-verifier' "$(git rev-parse --show-toplevel)"/tests/check_*.sh 2>/dev/null)
    for v in $vs; do bash "$v"; done
    

    Each reports what drifted and where; fix the docs it names, then re-run it. A repo with no such scripts runs nothing and moves on — that is not a failure.

  6. Commit the doc changes:

    git add CLAUDE.md README.md changelog.d/ CHANGELOG.md 2>/dev/null
    git commit -m "docs: update CLAUDE.md and changelog for <feature>"
    

Next steps

  • Run /orient to see what to work on next
  • Or run /ship if these doc changes need their own PR

Keep looking

Skills are one crate of 626,474. 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.