Workstyle — Docstrings

Enforce terse, WHY-only docstrings that document callable signatures. Project linter config wins; this skill fills gaps only.

When to Use

• Writing or editing any doc comment, docstring, or structured comment on a public symbol
• Adding a new function, method, class, interface, struct, or module with a comment block
• Editing code adjacent to an existing docstring (stale-comment removal is mandatory)
• /wk-workstyle-docstrings check <path> — audit a single file

Step 0: Resolve column width

Check project config priority order (defer to wk-workstyle Step 0 if already run). Use the first match found: