Update repository documentation from git diffs and validate Rustdoc and Python docstrings.
npx skills add https://github.com/Startti/colmena --skill documentation-startti
Please help me install this Agent Skill. Skill: documentation Source: https://github.com/Startti/colmena/tree/main/.agent/skills/documentation Command: npx skills add https://github.com/Startti/colmena --skill documentation-startti
Ensures repository documentation stays consistent with code changes so users and contributors can understand features correctly without relying on outdated or missing information.
///) and Python docstrings in sync with implementation details.Use the documentation skill when you modify code that affects behavior, public APIs, or docs, so the docs/ folder and in-code documentation reflect the latest implementation.
High-intent search queries and answers about installing and using this skill.
A git diff analysis for updating repository documentation covers detecting changed features, APIs, or user-facing behaviors, then updating relevant Markdown docs, Rustdoc comments, and Python docstrings to maintain consistency across the project.
To keep Rust and Python documentation consistent, analyze git diffs to detect behavioral or API changes, then update Rustdoc comments and Python docstrings alongside the `docs/` folder to match the latest implementation.
The best way to update repository docs after modifying public APIs is to analyze the git diff, update affected Markdown files and in-code docstrings, and then validate the generated output using `cargo doc` with consistency checks for links and examples.
Verify Rustdoc examples and links match the current code state by running `cargo doc` and performing documentation consistency checks to ensure generated docs, examples, and organizational structure align with the latest repository implementation.
Yes, this documentation workflow supports both Rust and Python projects by keeping Rustdoc and Python docstrings in sync with implementation details when features, APIs, or user-facing behaviors change in the repository.
Update technical documentation to avoid technical debt whenever code modifications affect behavior, public APIs, or user-facing features, ensuring the `docs/` folder and in-code documentation accurately reflect the current implementation without outdated information.
t-miura-024Analyze git repository changes and retrieve detailed diffs for modified files.
nicolasdaoAudit code diffs and generate documentation updates across docs and README.
JSai23Generate and update docstrings, rustdoc, JSDoc, and Go package comments from source code.
dt418Build documentation platforms with versioned docs, search, navigation, code highlighting, and API reference generation.