Codebases accumulate technical debt over time. This skill simplifies recently modified code to improve readability and consistency without changing functionality.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「simplify」を使用しています。 Complex nested conditional with ternary operators
期待される結果:
Refactored code using a switch statement or if/else chain that is easier to read and maintain
「simplify」を使用しています。 Code with overly terse variable names
期待される結果:
Code with clear, descriptive names that explain the purpose and intent of each variable
「simplify」を使用しています。 Function with mixed coding styles
期待される結果:
Consistent function declarations following project standards with proper type annotations
セキュリティ監査
安全All 8 static findings evaluated as false positives. The skill contains only documentation and coding standards references with no actual external commands, network code, or cryptographic algorithms. Safe for publication.
低リスクの問題 (1)
品質スコア
作れるもの
Post-Write Code Refinement
After implementing a new feature, use this skill to clean up the code before committing. It applies consistent coding standards and improves readability.
Technical Debt Reduction
Gradually improve code clarity during regular development by refining modified sections. Each refinement builds toward a more maintainable codebase.
Codebase Standard Enforcement
Ensure all new code follows project conventions. The skill references established standards from CLAUDE.md to maintain consistency.
これらのプロンプトを試す
Simplify the code you just wrote. Apply project coding standards and improve readability without changing functionality.
Review the recent changes and simplify any complex logic. Use switch statements instead of nested ternaries and make the code easier to understand.
Improve variable and function names in the recent code. Make them clear and descriptive while following project naming conventions.
Identify and eliminate redundant code in the recent changes. Consolidate repeated logic into shared helpers where appropriate.
ベストプラクティス
- Use the skill after each significant code change rather than waiting for large cleanup sessions
- Review the simplified code to ensure it still matches your original intent
- Combine with other skills like documentation generation for complete code improvement
回避
- Using the skill on code that has not been recently modified
- Expecting the skill to add new functionality or change behavior
- Applying overly aggressive simplification that reduces code clarity
- Skipping manual review of the simplified output