Code Reviewer
alirezarezvani/claude-skills
Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin, C, .NET, Java, C, C++, Rust, Ruby, PHP, and Dart/Flutter.
Applies opinionated production Python conventions chosen by the project's Python version: modern type syntax, pathlib, explicit checks and interface guidance.
Install Dignified Python Standards
$ npx skills add docling-project/docling --skill dignified-python -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install docling-project/docling dignified-python --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/docling-project/docling.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dignified-python .claude/skills/dignified-python && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dignified-python" agent skill from https://github.com/docling-project/docling/tree/main/.agents/skills/dignified-python into .claude/skills/dignified-python/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dignified-python", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/docling-project/docling/tree/main/.agents/skills/dignified-pythonType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add docling-project/docling --skill dignified-python -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install docling-project/docling dignified-python --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docling-project/docling.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/dignified-python .agents/skills/dignified-python && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dignified-python" agent skill from https://github.com/docling-project/docling/tree/main/.agents/skills/dignified-python into .agents/skills/dignified-python/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dignified-python", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add docling-project/docling --skill dignified-python -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install docling-project/docling dignified-python --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docling-project/docling.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/dignified-python .cursor/skills/dignified-python && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dignified-python" agent skill from https://github.com/docling-project/docling/tree/main/.agents/skills/dignified-python into .cursor/skills/dignified-python/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dignified-python", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/docling-project/docling.git --path .agents/skills/dignified-python--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add docling-project/docling --skill dignified-python -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install docling-project/docling dignified-python --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docling-project/docling.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/dignified-python .gemini/skills/dignified-python && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dignified-python" agent skill from https://github.com/docling-project/docling/tree/main/.agents/skills/dignified-python into .gemini/skills/dignified-python/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dignified-python", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install docling-project/docling dignified-pythonInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add docling-project/docling --skill dignified-python -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/docling-project/docling.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/dignified-python .github/skills/dignified-python && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dignified-python" agent skill from https://github.com/docling-project/docling/tree/main/.agents/skills/dignified-python into .github/skills/dignified-python/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dignified-python", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add docling-project/docling --skill dignified-python -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install docling-project/docling dignified-python --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docling-project/docling.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/dignified-python .opencode/skills/dignified-python && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dignified-python" agent skill from https://github.com/docling-project/docling/tree/main/.agents/skills/dignified-python into .opencode/skills/dignified-python/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dignified-python", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dignified-python- GitHub stars
- 69k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 545 words
- Files
- 16 (incl. references)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Applies opinionated production Python conventions chosen by the project's Python version: modern type syntax, pathlib, explicit checks and interface guidance.
- Works in 4 steps: pyproject.toml - Look for… → setup.py or setup.cfg - Look for… → .python-version file - Contains version… → …
- Writing new Python code to modern, production-style conventions
- SKILL.md covers When to Use This Skill, When to Use This Skill vs.…, Core Knowledge (ALWAYS Loaded) and Version Detection, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
The skill is general-purpose Python style guidance, not tied to any framework, and a project's own conventions can override it. It always loads a core guidance file, then detects the minimum Python version by checking requires-python in pyproject.toml, python_requires in setup.py or setup.cfg and a .python-version file, defaults to Python 3.12 if none is found, and loads the matching version file for 3.10, 3.11, 3.12 or 3.13.
It is invoked for requests to make code more Pythonic and for questions about type hints, LBYL versus EAFP exception handling, pathlib versus os.path, CLI patterns with click, and general code review or quality. Its leaning is toward looking before you leap, with explicit condition checks. Reference files cover module design, checklists, API design, exception handling, interfaces and advanced typing, with further notes on CLI patterns and subprocess use. Dagster-specific questions are routed to other skills.
When your agent uses it
- Writing new Python code to modern, production-style conventions
- Reviewing or refactoring Python for type hints, pathlib and exception handling
- Deciding between LBYL and EAFP in a piece of code
- Structuring a Python command-line tool
Example prompts
- “Make this module more Pythonic and add modern type hints.”
- “Replace the os.path calls in this script with pathlib.”
- “Review this function: should it check conditions first or catch exceptions?”
- “Refactor this click command so the logic is easy to test.”
Requirements
- A Python project, version 3.10 to 3.13
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- pyproject.toml - Look for requires-python field (e.g., requires-python = ">=3.12")
- setup.py or setup.cfg - Look for python_requires
- .python-version file - Contains version like 3.12 or 3.12.0
- Default to Python 3.12 if no version specifier found
What it can do on your machine
Read from SKILL.md and the folder at commit 638c43a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Dignified Python Standards loads about 1.5k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 78 tokens; SKILL.md has 545 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from docling-project/docling at commit 638c43a, republished under its Apache-2.0 licence (© docling-project). 545 words, ~1,479 tokens.
Download SKILL.mdSave it as
.claude/skills/dignified-python/SKILL.md (or your agent's skills folder). This skill also uses 15 other files; get the full folder from GitHub.- name
- dignified-python
- description
- Opinionated production Python standards with automatic version detection (3.10-3.13). Use when writing, reviewing, or refactoring Python in repos that want modern type syntax, explicit condition checks where practical, pathlib operations, interface guidance, and pragmatic production patterns.
- references
- dignified-python-core, cli-patterns, versions/python-3.10, versions/python-3.11, versions/python-3.12, versions/python-3.13, references/advanced/api-design…
Dignified Python
Opinionated Python guidance for writing clean, maintainable, modern Python code (versions 3.10-3.13).
When to Use This Skill
Auto-invoke when users ask about:
- "make this pythonic" / "is this good python"
- "type hints" / "type annotations" / "typing"
- "LBYL vs EAFP" / "exception handling"
- "pathlib vs os.path" / "path operations"
- "CLI patterns" / "click usage"
- "code review" / "improve this code"
- Any Python code quality or standards question
Note: This skill is general-purpose Python style guidance, not Dagster-specific. It captures one explicit, LBYL-leaning set of conventions; project conventions can override it when needed.
When to Use This Skill vs. Others
| User Need | Use This Skill | Alternative Skill |
|---|---|---|
| "make this pythonic" | ✅ Yes - Python standards | |
| "is this good python" | ✅ Yes - code quality | |
| "type hints" | ✅ Yes - typing guidance | |
| "LBYL vs EAFP" | ✅ Yes - exception patterns | |
| "pathlib vs os.path" | ✅ Yes - path handling | |
| "best practices for dagster" | ❌ No | /dagster-best-practices |
| "implement X pipeline" | ❌ No | /dg for implementation |
| "which integration to use" | ❌ No | /dagster-expert |
| "CLI argument parsing" | ✅ Yes - CLI patterns |
Core Knowledge (ALWAYS Loaded)
@dignified-python-core.md
Version Detection
Identify the project's minimum Python version by checking (in order):
pyproject.toml- Look forrequires-pythonfield (e.g.,requires-python = ">=3.12")setup.pyorsetup.cfg- Look forpython_requires.python-versionfile - Contains version like3.12or3.12.0- Default to Python 3.12 if no version specifier found
Once identified, load the appropriate version-specific file:
- Python 3.10: Load
versions/python-3.10.md - Python 3.11: Load
versions/python-3.11.md - Python 3.12: Load
versions/python-3.12.md - Python 3.13: Load
versions/python-3.13.md
Conditional Loading (Load Based on Task Patterns)
Core files above cover 80%+ of Python code patterns. Only load these additional files when you detect specific patterns:
Pattern detection examples:
- If task mentions "click" or "CLI" -> Load
cli-patterns.md - If task mentions "subprocess" -> Load
subprocess.md
Reference Documentation Structure
This skill's reference material is organized by topic:
Core References
dignified-python-core.md- Essential standards (always loaded)cli-patterns.md- Command-line interface patterns (click, argparse)
Version-Specific References (versions/)
python-3.10.md- Features available in Python 3.10+python-3.11.md- Features available in Python 3.11+python-3.12.md- Features available in Python 3.12+python-3.13.md- Features available in Python 3.13+
Show full SKILL.md (220 more words)Show less
Advanced Topics (references/advanced/)
exception-handling.md- LBYL patterns, error boundariesinterfaces.md- ABC and Protocol patternstyping-advanced.md- Advanced typing patternsapi-design.md- API design principles
When to Read Each Reference Document
references/advanced/exception-handling.md
Read when:
- Writing try/except blocks
- Wrapping third-party APIs that may raise
- Seeing or writing
from eorfrom None - Unsure if LBYL alternative exists
references/advanced/interfaces.md
Read when:
- Creating ABC or Protocol classes
- Writing @abstractmethod decorators
- Designing gateway layer interfaces
- Choosing between ABC and Protocol
references/advanced/typing-advanced.md
Read when:
- Using typing.cast()
- Creating Literal type aliases
- Narrowing types in conditional blocks
references/module-design.md
Read when:
- Creating new Python modules
- Adding module-level code (beyond simple constants)
- Using @cache decorator at module level
- Seeing Path() or computation at module level
- Considering inline imports
references/advanced/api-design.md
Read when:
- Adding default parameter values to functions
- Defining functions with 5 or more parameters
- Using ThreadPoolExecutor.submit()
- Reviewing function signatures
references/checklists.md
Read when:
- Final review before committing Python code
- Unsure if you've followed all rules
- Need a quick lookup of requirements
How to Use This Skill
- Core knowledge is loaded automatically (defaults, pathlib, imports, anti-patterns)
- Version detection happens once - identify the minimum Python version and load the appropriate version file
- Reference documents are loaded on-demand based on the triggers above
- Additional patterns may require extra loading (CLI patterns, subprocess)
- Each file is self-contained with complete guidance for its domain
© docling-project, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 15 other files (references) in .agents/skills/dignified-python of docling-project/docling.
- SKILL.md
- LICENSE
- cli-patterns.md
- dignified-python-core.md
- references/README.md
- references/advanced/api-design.md
- references/advanced/exception-handling.md
- references/advanced/interfaces.md
- references/advanced/typing-advanced.md
- references/checklists.md
- references/module-design.md
- subprocess.md
- versions/python-3.10.md
- versions/python-3.11.md
- versions/python-3.12.md
- versions/python-3.13.md
Open the folder on GitHubat commit 638c43a
Compare with similar skills
Dignified Python Standards next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dignified Python Standards this skilldocling-project/docling | 69k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Code Revieweralirezarezvani/claude-skills | 28k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Code ReviewerLeoYeAI/openclaw-master-skills | 2.2k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Code Reviewerborghei/Claude-Skills | 881 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Framer SDK Patternsjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Clean Code GuardamElnagdy/guard-skills | 1.3k | 2 repos | ~4.3k | Automated safety check: Pass | MIT |
Similar skills
Code Reviewer
LeoYeAI/openclaw-master-skills
Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin.
Code Reviewer
borghei/Claude-Skills
Code review automation for TypeScript, JavaScript, Python, Go, Swift, and Kotlin.
Framer SDK Patterns
jeremylongshore/tons-of-skills-marketplace
Apply production-ready Framer SDK patterns for TypeScript and Python.
Clean Code Guard
amElnagdy/guard-skills
Reviews generated or changed production code against Clean Code, SOLID, DRY, KISS, YAGNI and LLM-specific failure modes before it ships, in any language.
Code Review Skill
awesome-skills/code-review-skill
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…
More from docling-project/docling
Building Pydantic AI Agents
docling-project/docling
Patterns and tested examples for building agents with Pydantic AI: tools, capabilities, structured output, dependency injection, hooks, YAML specs, streaming and testing.
Docling Document Conversion
docling-project/docling
Converts PDFs, Office files, HTML, images and other documents into a unified DoclingDocument with Markdown or JSON output, through the docling CLI, Python SDK or a remote service.
Docling Pull Request Review
docling-project/docling
Reviews or re-reviews a Docling pull request in fixed stages, with findings that can be reproduced and an explicit record of every check that was run.
Related
Works with
Categories
Questions about Dignified Python Standards
What does Dignified Python Standards do?
Applies opinionated production Python conventions chosen by the project's Python version: modern type syntax, pathlib, explicit checks and interface guidance. The skill is general-purpose Python style guidance, not tied to any framework, and a project's own conventions can override it.13.
When should I use Dignified Python Standards?
Dignified Python Standards fits situations like: writing new Python code to modern, production-style conventions; reviewing or refactoring Python for type hints, pathlib and exception handling; deciding between LBYL and EAFP in a piece of code; structuring a Python command-line tool.
How do I install Dignified Python Standards in Claude Code?
Run `npx skills add docling-project/docling --skill dignified-python -a claude-code`. Or copy the skill folder (.agents/skills/dignified-python in docling-project/docling) into .claude/skills/dignified-python in your project. Claude Code loads it when a task matches its description.
How do I install Dignified Python Standards in Codex?
Run `npx skills add docling-project/docling --skill dignified-python -a codex`. Or copy the skill folder (.agents/skills/dignified-python in docling-project/docling) into .agents/skills/dignified-python in your project. Codex loads it when a task matches its description.
Can I use Dignified Python Standards in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add docling-project/docling --skill dignified-python -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dignified-python, .gemini/skills/dignified-python, .github/skills/dignified-python and .opencode/skills/dignified-python in your project.
What does Dignified Python Standards need to run?
SKILL.md names no scripts, command-line tools or credentials: Dignified Python Standards is instructions for the agent only. Our summary lists: A Python project, version 3.10 to 3.13.
Does Dignified Python Standards access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Dignified Python Standards safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Dignified Python Standards use?
Dignified Python Standards is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Dignified Python Standards use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 10k tokens, read only when the agent opens those files.
What are the alternatives to Dignified Python Standards?
Skills that share tags, products or a category with Dignified Python Standards: Code Reviewer (alirezarezvani/claude-skills, 28k stars), Code Reviewer (LeoYeAI/openclaw-master-skills, 2.2k stars), Code Reviewer (borghei/Claude-Skills, 881 stars) and Framer SDK Patterns (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dignified Python Standards?
docling-project (a GitHub organization) maintains it in docling-project/docling, which has 68,515 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 8, 2026.
Source: docling-project/docling on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.