An open-source AI engineering skill package that turns code changes into three outputs:
- implementation
- human-friendly explanation
- persistent project documentation
This skill is designed for teams that want AI coding help without losing architectural clarity or team memory over time.
When the skill is used, the AI assistant should:
- explain code changes in chat in a teaching-oriented format
- update
docs/CHANGELOG.mdafter file changes - update
docs/ARCHITECTURE.mdwhen structure or data flow changes - describe execution flow, dependencies, and system fit
- provide a recommended reading order for learners
implementation-explainer/
|-- README.md
|-- README.zh-CN.md
|-- LICENSE
|-- .gitignore
|-- skill/
| `-- implementation-explainer/
| |-- SKILL.md
| `-- references/
| `-- documentation-rules.md
|-- scripts/
| |-- install_skill.py
| `-- validate_project.py
`-- docs/
|-- ARCHITECTURE.md
|-- CHANGELOG.md
`-- RELEASE_CHECKLIST.md
python scripts/install_skill.pyBy default this copies the skill into:
- Windows:
%USERPROFILE%\\.ai-skills\\implementation-explainer - macOS/Linux:
$HOME/.ai-skills/implementation-explainer
python scripts/install_skill.py --target-dir /path/to/skills/implementation-explainerAfter installation, add the implementation-explainer skill to your AI coding workflow when you want:
- code plus explanation
- enforced changelog updates
- architecture memory
- learning-oriented change walkthroughs
- Create a new GitHub repository from this folder.
- Push the repository.
- Version future skill changes with tags or releases.
- Share the repo URL so others can clone and install it with the included script.
Run the built-in project validation:
python scripts/validate_project.pyThen run a clean installation check:
python scripts/install_skill.py --target-dir .ai-skills-test/implementation-explainerFor a final manual review, use docs/RELEASE_CHECKLIST.md.
AI coding is much more useful when it also leaves behind:
- clear rationale
- architecture knowledge
- onboarding-friendly explanations
- durable project memory
This skill makes those behaviors explicit and repeatable.
Today this skill can:
- enforce a structured post-change explanation in chat
- require
docs/CHANGELOG.mdupdates after implementation work - require
docs/ARCHITECTURE.mdupdates when structure or data flow changes - separate new files from modified files in explanations
- explain execution flow, module interaction, and system fit
- provide a learner-friendly reading order
- capture design decisions, risks, and assumptions
- package the skill in a reusable repository with an install script