commenting-code

Review Python code comments and docstrings for redundancy.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/othercode/profiles --skill commenting-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commenting-code
Source: https://github.com/othercode/profiles/tree/main/plugins/django-engineering/skills/commenting-code
Command: npx skills add https://github.com/othercode/profiles --skill commenting-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers write more effective code comments and docstrings by distinguishing between useful and redundant documentation, leading to cleaner, more maintainable codebases.

Core Features & Use Cases

  • Comment Quality Assessment: Identifies and suggests removal of comments that merely restate code functionality.
  • Docstring Best Practices: Enforces the use of docstrings for explaining the "why" behind code, documenting interfaces, and providing UI-specific information (like help_text).
  • Use Case: When reviewing a pull request, this Skill can flag comments that are redundant, helping the author to remove them and focus on documentation that adds real value.

Quick Start

Use the commenting-code skill to review the docstrings and comments in the current Python file.

Frequently Asked Questions about commenting-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify useless code comments in Python?

Effective Python docstrings focus on explaining the why behind code logic, documenting interfaces, and providing UI-specific information like help_text. This skill enforces these best practices by flagging comments that merely describe functionality.

What is the best way to review Python docstrings in a pull request?

The best way to review Python docstrings in a pull request is to check for redundant comments that state what the code does. This skill flags those annotations so authors can remove them and focus on documentation providing real value.

When should I write code comments versus docstrings in Python?

Write Python docstrings to document interfaces and explain the why behind code, while avoiding comments that merely restate what the code does. This skill enforces these rules to distinguish useful annotations from useless ones.

Does this code review skill work with Python files only?

Yes, this code review skill works with Python files, enforcing specific rules for writing and reviewing Python code comments and docstrings to ensure they explain the why rather than the what.

Why should I remove comments that state what the code does?

You should remove comments that state what the code does because they are redundant and clutter the codebase. Removing them enforces best practices, leading to cleaner, more maintainable code with documentation that adds real value.