← ClaudeAtlas

python-commentslisted

How Tsukini writes comments in Python - the Python equivalent of cpp-comments, from his scripts (libutils cmake/scripts, MAGIC) - the Xartania header (63 double quotes), the
TsukiNi22/ai-utils · ★ 1 · AI & Automation · score 74
Install: claude install-skill TsukiNi22/ai-utils
# Tsukini comment style (Python) `<name>` (a skill) = the folder of that skill: `~/.claude/skills/<name>` (setup.sh) or `${CLAUDE_SKILL_DIR}/../../*/<name>` (plugin of the marketplace). Always in **English**, short, no final period. Comment the **why** and the non-obvious, never paraphrase the code. General rules of every language: `comments` (section 1). Code style: `python-style`. When a file already has its own comment style (an older file of MAGIC with `""" Import """` banners), the local style wins. ## 1. Structure comments (exact strings) - File header: `python3 <cpp-class>/scripts/header.py --file <name>.py --desc "..."` (63 `"`, banner, `Edition:` / `File Name:` / `File Description:` with `##` lines), never written by hand. - Section banners, at column 0, one empty line before: `##### Import #####`, `##### Const #####`, `##### Tools #####`, `##### Class #####`, `##### Program #####`, `##### Declaration #####`, `##### Tests #####` (only the used ones). - Import labels (exact): `# Import that can't be in the try`, `# Import that can be checked`; the optional install block `# Try to install dependencies (failsafe)`; the guard comments `# Check if the program is call and not imported` / `# Check if the program is imported and not call` (the user's wording, kept as is). ## 2. Trailing comments (the most used) ```python from pathlib import Path # Used to create & edit files and to get the file name exit(255) # Special exit code (only place used) data = {