Claude-skill-registry documentation-process

Name: documentation-process
Author: majiayu000

After implementing a new feature or fixing a bug, make sure to document the changes. Use after finishing the implementation phase for a feature or a bug-fix

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/documentation-process" ~/.claude/skills/majiayu000-claude-skill-registry-documentation-process && rm -rf "$T"

manifest: skills/data/documentation-process/SKILL.md

Documentation Process

Guidelines

After completing a new feature, always see if you need to update the Architecture documentation at
```
/docs/contributing/ARCHITECTURE.md
```
and Test documentation in
```
/docs/contributing/TESTING.md
```
for other developers, so anyone could easily pick up the work and understand the project and the feature that was added.
If the code change included prior decision-making out of several alternatives, document an ADR at
```
/docs/adr
```
for any non-trivial/non-obvious decisions that should be preserved.