Write effective code comments, READMEs, and technical documentation following intent-first principles. Use when adding comments, writing docstrings, creating READMEs, or updating any documentation.
83
77%
Does it follow best practices?
Impact
96%
1.14xAverage score across 3 eval scenarios
Passed
No known issues
Fix and improve this skill with Tessl
tessl review fix ./.github/skills/common/common-documentation/SKILL.mdREADME structure with Mission, Onboarding, and Maintenance sections
Mission statement
91%
100%
Prerequisites listed
100%
100%
Installation steps
100%
100%
Usage instructions exact
100%
100%
Inputs/outputs documented
100%
100%
Known quirks documented
100%
100%
Fixes or workarounds
100%
100%
No orphan TODO
100%
100%
No placeholder text
100%
100%
Maintenance section present
75%
75%
Intent-first comments and JSDoc on TypeScript module
Intent-first inline comments
91%
83%
JSDoc on public members
100%
100%
JSDoc @param tags
100%
100%
JSDoc @returns tag
100%
100%
Usage example in JSDoc
0%
100%
No commented-out code
100%
100%
TODO format with owner
100%
100%
TODO ticket reference
100%
100%
No bare TODO
100%
100%
No what-comments
90%
90%
OpenAPI spec, Mermaid diagram, and ADR for a new service
OpenAPI/Swagger format
100%
100%
Endpoints documented in spec
100%
100%
Copy-pasteable examples
30%
50%
Mermaid diagram present
0%
100%
ADR file location
0%
100%
ADR contains rationale
100%
100%
Contract-first approach
100%
100%
No bare TODO
100%
100%
Response schema defined
100%
100%
No implementation code
100%
100%
de793e9
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.