Enforce consistent code naming conventions across a project.
npx skills add https://github.com/Aliisa-yt/twitchbot --skill naming-rules-aliisa-yt
Please help me install this Agent Skill. Skill: naming-rules Source: https://github.com/Aliisa-yt/twitchbot/tree/main/.github/skills/naming-rules Command: npx skills add https://github.com/Aliisa-yt/twitchbot --skill naming-rules-aliisa-yt
This Skill ensures consistent and understandable naming conventions across the project, improving code readability and maintainability.
Apply the project's naming conventions to the new function calculate_user_score.
High-intent search queries and answers about installing and using this skill.
To enforce consistent code naming, apply a prioritized order using external specifications, existing project patterns, and PEP 8 guidelines. This prevents inconsistencies and improves readability for classes, methods, variables, and files.
Safe renaming requires following structured procedures to maintain backward compatibility and prevent semantic drift. You must apply project conventions and verify changes through testing to avoid breaking existing API compatibility.
PEP 8 guidelines include specific naming rules for test functions and private members. You should prioritize external specs first, then project conventions, to ensure these elements adhere to established standards.
To standardize naming for new features, consult prioritized rules that check external specifications and existing project patterns first. This ensures new functions, variables, and files match established conventions.
You should prioritize external specifications over PEP 8 code style when defined specs exist for your project. This ensures your naming convention respects external requirements before falling back to standard guidelines.
Naming convention rules for constants, classes, and files prioritize external specs, then project patterns, then PEP 8. This structured approach improves code readability and maintainability across the project.
rsmdtIdentify codebase patterns to enforce naming, architecture, and testing conventions.
dougwithseismicPlan and execute multiple interdependent features with automated TDD and code review workflows.
PriyanshKuniyalEnforce PEP 8 formatting, naming, and documentation standards in Python code.
POWERFULMOVESRename identifiers and replace patterns across multiple code files.
