Loading...
Loading...
Found 87 Skills
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when refining recently modified code unless instructed otherwise.
Code refactoring best practices based on Martin Fowler's catalog and Clean Code principles (formerly refactoring). This skill should be used when refactoring existing code, improving code structure, reducing complexity, eliminating code smells, or reviewing code for maintainability. Triggers on tasks involving extract method, rename, decompose conditional, reduce coupling, or improve readability.
Use when tempted to write clever code. Use when solution feels complex. Use when showing off skills instead of solving problems.
Use when reviewing code changes, pull requests, branches, or work-in-progress diffs for correctness, intent fit, repo-local architecture, surrounding-code pattern mismatches, maintainability, naming, tests, and over-engineering. Runs a git-heavy, subagent-oriented review that reads local AGENTS.md/docs/plans/conversation/PR context before judging the diff.
Create Scratch project with TypeScript using Hikkaku; use when the user asks how to build or structure a Scratch project in this repo.
Python refactoring for readability, maintainability, and performance.
Agent skill for reviewer - invoke with $agent-reviewer
Analyzes code comments for accuracy, completeness, and long-term maintainability. Identifies misleading comments, comment rot, and documentation gaps. Triggers: After adding documentation, before finalizing a PR, when reviewing comments. Examples: - "Check if the comments are accurate" -> verifies comments match code behavior - "Review the documentation I added" -> analyzes new comments for quality - "Analyze comments for technical debt" -> finds outdated or misleading comments - "Are my docstrings correct?" -> validates documentation accuracy
Improve existing code through safe, behavior-preserving Clean Code refactoring. Use when the user asks to refactor code, clean up messy code, improve readability, simplify structure, reduce duplication, improve naming, review maintainability, or apply Clean Code principles. Do not use for broad architecture redesign unless the user asks for redesign.
This skill should be used when engineering decisions are being made during code implementation. The Archivist enforces decision documentation as a standard practice, ensuring every engineering choice includes rationale and integrates with Architecture Decision Records (ADRs). Use when writing code that involves choosing between alternatives, selecting technologies, designing architectures, or making trade-offs.
Reviews changes for correctness, edge cases, style, security, and maintainability with severity levels (Blocker/Major/Minor/Nit). Use before finalizing changes.
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.