Assumption: each TODO represents a real follow-up rather than intentionally deferred work. 1. Inventory every TODO and assign an owner. 2. Create or link a ticket for each actionable item. 3. Rewrite comments using the required format: ```ts // TODO(alice): Explain why retry jitter is required to prevent the thundering herd. // Ticket: PROJ-123 ``` 4. Make comments explain `why`, not mechanics or obvious code behavior. 5. Convert public API comments to JSDoc, including `Args`, `Returns`, and ...
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill common-documentation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Common Documentation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-common-documentation-58f1a493)More formats (shields.io, HTML) on the badges page.
Assumption: each TODO represents a real follow-up rather than intentionally deferred work.
1. Inventory every TODO and assign an owner.
2. Create or link a ticket for each actionable item.
3. Rewrite comments using the required format:
```ts
// TODO(alice): Explain why retry jitter is required to prevent the thundering herd.
// Ticket: PROJ-123
```
4. Make comments explain `why`, not mechanics or obvious code behavior.
5. Convert public API comments to JSDoc, including `Args`, `Returns`, and a `Usage` example where applicable.
6. Delete obsolete or commented-out code; recover it through Git history if needed.
7. Remove TODOs that are completed, invalid, or no longer needed.
8. Add a review/check that rejects new orphan TODOs without an owner and ticket reference. Documentation should ship with the related feature.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.
