Brendan Murphy

You can run read-only documentation audits with gap analysis, review code or configuration changes for documentation impact with bounded same-change updates, author or revise coherent documentation sets, and review Python docstrings against repository policy, public API declarations, and tests.

They target research software engineers and developers maintaining technical or scientific software, such as atmospheric chemistry research codebases, who need structured documentation audits, pull-request documentation review, or policy-driven Python docstring checks.

Use documentation-assessment for read-only audits, context discovery, and prioritised documentation needs maps. Use documentation-impact-review when a code, configuration, CLI, schema, or workflow change requires documentation consequence analysis and bounded same-change updates during pull-request review.

It covers only Python docstrings affected by a code change, using repository policy, public API declarations, source, annotations, and tests. It explicitly excludes tutorials, general prose, and site-wide documentation audits, which belong to the other documentation skills.

They require access to the target repository, including its documentation files, source code, tests, and any repository documentation policy. For impact review, a pull request or diff is needed; for authoring, a clear user request for documentation file changes is required.