fix-members-short-description
Automated helper for refining and correcting short descriptions of Python class members.
Install
mkdir -p .claude/skills/fix-members-short-description && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7237" && unzip -o skill.zip -d .claude/skills/fix-members-short-description && rm skill.zipInstalls to .claude/skills/fix-members-short-description
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when asked to fix short descriptions of Python type members.Key capabilities
- →Parse Python docstrings for type members
- →Identify vague or incorrect short descriptions
- →Rewrite descriptions to follow standard patterns
- →Wrap lines at 88 characters
- →Add noqa: E501 for unbreakable tokens
How it works
It scans Python docstrings, identifies the first sentence, and reformats it into multiple lines using the backslash character for proper documentation generation.
Inputs & outputs
When to use fix-members-short-description
- →Standardize member documentation
- →Fix ambiguous type member descriptions
- →Improve code readability in Python projects
About this skill
Inputs
- File or directory with Python modules.
Instructions
When Flet documentation is generated from docstrings the first sentence of a member docstring is used as a short description, for example:
@dataclass
class MyControl:
property_a: str
"""
Short description of a property.
Full description.
Another line of full description.
"""
Here "Short description of a property." will be used as a short description.
However, when a sentence is broken into multiple lines the lines must be "concatenated" with \, for example:
@dataclass
class MyControl:
property_a: str
"""
Short description of a property which could \
take multiple lines.
Full description.
Another line of full description.
"""
Your goal is to go through all members (properties, methods, etc.) of all types (classes, enums) in input file or directory and ensure the first sentence in their docstrings is broken into multiple lines correctly with \ symbol.
Apply the fix regardless of whether the first sentence starts on the same line as the opening """ or on a following line.
Ensure every docstring line is at most 88 characters long (including any trailing \). If a line cannot be wrapped without breaking a single unbreakable token (e.g., a long URL or Windows registry path like HKEY_LOCAL_MACHINE\\...), add # noqa: E501 to the docstring closing """ line instead of the long line.
When not to use it
- →When the docstrings are already compliant with standards
- →When the input is not a Python project
Limitations
- →Requires manual review of complex docstring structures
- →Limited to Python type members
How it compares
It automates the standardization of docstrings instead of manual editing.
Compared to similar skills
fix-members-short-description side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| fix-members-short-description (this skill) | 1 | 4mo | No flags | Beginner |
| deepwiki-rs | 25 | 9mo | Review | Intermediate |
| python-code-style | 9 | 6mo | Review | Intermediate |
| cookbook-audit | 5 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by flet-dev
View all by flet-dev →You might also like
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
python-code-style
wshobson
Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.
cookbook-audit
anthropics
Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.
code-style-guide
OpenHands
Project coding standards and style guidelines. Always follow these conventions when writing or reviewing code.
code-changelog
bear2u
AI가 만든 모든 코드 변경사항을 reviews 폴더에 기록하고 간단한 HTML 뷰어로 웹 브라우저에서 실시간 확인할 수 있습니다. 매 수정마다 문서가 생성되고 Python 서버로 즉시 확인 가능합니다.
test-knowledge
uchicago-bfi-gnlab
Generates a quiz to test the user's knowledge of a codebase or script. Supports two modes: script-specific (deep dive on one script, invoke with a script path) and whole-project (architecture, design choices, pipeline, invoke with `project`). Reads actual source files, git history, and directory str