dignified-code-simplifier_skill

Overview

This skill simplifies and refines Python code for clarity, consistency, and maintainability while preserving exact functionality. It applies the dignified-python standards and focuses on files recently modified in the current session unless told to inspect a broader scope. The goal is readable, explicit code that is easier to maintain and review.

How this skill works

The skill scans recently edited Python files, identifies candidates for simplification, and proposes or applies refinements that do not change behavior. It prioritizes proactive checks (LBYL), pathlib usage, absolute imports, O(1) properties, limited indentation depth, and clear variable placement. Changes concentrate on reducing unnecessary nesting, removing redundant logic, clarifying names, and consolidating related code while preserving all outputs and side effects.

When to use it

• After implementing a feature or bug fix to keep new code consistent with project standards.
• During code review to simplify complex or deeply nested functions without altering behavior.
• When refactoring to improve readability prior to adding new features or tests.
• To enforce dignified-python rules across recently changed modules.
• Before merging changes to reduce technical debt introduced by recent edits.

Best practices

• Only modify files that were recently touched in this session unless explicitly requested to broaden scope.
• Prefer explicit condition checks (LBYL) over using exceptions for control flow.
• Use pathlib.Path and explicit encoding for file operations; avoid os.path.
• Keep properties and magic methods O(1); move I/O or iteration to explicit methods.
• Limit nesting to four levels by extracting helpers; declare variables close to use.

Example use cases

• Simplifying a newly added function that contains nested conditionals and redundant checks.
• Refactoring a modified module to replace relative imports with absolute imports and clearer names.
• Replacing file handling using os.path/open with pathlib.Path and explicit encoding in recently edited files.
• Extracting helper functions when a recent change introduced deep nesting, preserving original behavior.
• Cleaning up temporary debugging branches left in modified code to produce clearer, production-ready logic.