Loading...
Loading...
Found 41 Skills
Python development best practices including PEP 8 style guidelines, type hints, docstring conventions, and common patterns. Use when writing or modifying Python code.
Rewrite Python docs and docstrings from source code. Use when Codex needs to refresh the docs.
Adds and enhances comments and documentation comments in code. Use with requests like 'add comments', 'write comments', 'enhance comments', 'add JSDoc', 'add docstring', 'add documentation comments'. Preserve role boundaries from the package/service perspective, prerequisites and contracts between callers and callees, and context from other files/services in a 'readable on the spot' format. Do not modify the code itself (for implementation changes, use implement-issue). Refer to code-comment-style for detailed rules, create-commit for commit creation, and update-docs for CLAUDE.md synchronization.
Trim and freshen technical documents, READMEs, design notes, PR descriptions, internal messages, and source-code comments or docstrings. Uses independent fresh-reader reviews to expose author-context bias, then deletes repetition, defensive caveats, filler, decorative structure, and code restatements while preserving facts, decisions, actions, constraints, and necessary rationale. Use when text is overexplained, repetitive, hard to scan, written while thinking, or when comments restate code or have drifted out of sync with it.
Write Python docstrings following the Google Python Style Guide, using clear sections and examples.
Code Style Conventions. Use when writing, editing, or reviewing Python code. This includes conventions such as type hints, Decimal precision, docstrings, module organization, etc. Enforces type hints, Decimal precision, docstrings, and module organization.
Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.
Documentation conventions for NeMo-RL. Covers docs/index.md updates and docstring format. Do NOT use for: bug fixes, test fixes, dependency bumps, refactoring, CI/CD changes, performance tuning, or any task that does not involve writing or updating documentation.
Review generated or changed documentation before it ships — READMEs, API references, docstrings, PHPDoc/JSDoc, changelogs, tutorials, and doc sites. Best used reactively after an agent writes or edits docs, after code changes documented behavior, or before publishing docs. Use when the user says 'review the docs', 'is this documentation accurate', 'update the docs', 'write a README', 'document this API', 'add a docstring', or 'add a changelog entry'. Core job: verify every referenced function, flag, endpoint, config key, and code sample against the source; catch docs-vs-code drift; strip filler and unverifiable claims. DO NOT USE for production code review (use clean-code-guard), test review (use test-guard), marketing copy or blog posts, prose style editing of non-technical writing, or documentation site theming.
Audit code comments and docstrings quality across 6 categories (WHY-not-WHAT, Density, Forbidden Content, Docstrings, Actuality, Legacy). Use when code needs comment review, after major refactoring, or as part of ln-100-documents-pipeline. Outputs Compliance Score X/10 per category + Findings + Recommended Actions.
Expert guidance for writing clear, comprehensive documentation including READMEs, API docs, docstrings, and technical guides. Use when creating or improving documentation.
Checks WHY-not-WHAT, density (15-20%), forbidden content, docstrings quality, actuality, legacy cleanup. Returns findings with severity, location, and recommendations.