Loading...
Loading...
Found 63 Skills
Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks.
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through diagnosing the failure via OPENCLI_DIAGNOSTIC, patching the adapter, and retrying. Works with any AI agent.
Check or verify whether a Skill complies with best practice specifications, covering naming conventions, directory structure, metadata integrity, temporary file cleanup, and dependency format validation. It provides detailed checklists, automatic repair suggestions, and report templates, and also supports integrity checks and automatic repair of skill library documentation. It is suitable for quality verification after creating or modifying a Skill
Validates Stories/Tasks or context via parallel multi-agent review (Codex + Gemini). Merges findings, debates, applies fixes. GO/NO-GO verdict.
Technical debt detection and remediation. Run at session end to find duplicated code, dead imports, security issues, and complexity hotspots. Triggers: 'find tech debt', 'scan for issues', 'check code quality', 'wrap up session', 'ready to commit', 'before merge', 'code review prep'. Always uses parallel subagents for fast analysis.
Systematic detection and prioritization of neglected code quality issues: stale TODOs, unused imports, deprecated functions, high complexity, dead code. Use when user requests "code cleanup", "find TODOs", "technical debt scan", or "quality of life fixes". Do NOT use for bug fixing (use systematic-debugging), feature work (use test-driven-development), or formatting-only (use code-linting).
[DevOps & Infra] Run linters and fix issues for backend or frontend
Diagnose and fix oh-my-claudecode installation issues
Scans the current project's frontend files, finds the components most out of alignment with .marrow.md, and fixes them automatically — without the user specifying a target. The zero-argument soul alignment sweep. Use this skill when the user wants to broadly align the project to the design soul, fix whatever is most off without specifying a file, or run a soul sweep across multiple components at once. Triggers on: /marrow-magic, or prompts like "fix everything to match marrow", "align my whole project", "soul sweep", "fix the worst violations", "everything feels off", "clean up all components to match the design". Requires .marrow.md to exist. If not found, instructs user to run /marrow first.
Use when iterative review-fix cycles are needed on a plan or implementation — bounded loop with severity gating, automatic fixes, and finding disposition.
Salesforce debugging and troubleshooting skill with log analysis, governor limit detection, and agentic fix suggestions. Parse debug logs, identify performance bottlenecks, analyze stack traces, and automatically suggest fixes.
Novel Logic/Plot Review, applicable to user requests such as "Help me check if there are bugs in my novel", "Check if there are timeline contradictions", "Check if characters are OOC", "Find plot conflicts between different parts", "Sort out whether foreshadowings are resolved", "Check the rationality of novel plots", "Check if there are plot loopholes", "Character behaviors are inconsistent with their personalities", "Check if the timeline is correct", "Find contradictions in the novel", "Help me sort out all foreshadowings", "Novel plot bug check", "Logical loophole troubleshooting", etc. It detects issues such as timeline conflicts, logical loopholes, character OOC, and missing foreshadowings. **Performs word count checks to ensure chapter word counts meet standards**, **generates a detailed issue list and automatically fixes all issues, with the fixed results directly modifying the chapters/ directory and automatically backing up the original files to .sumeru/write/original/ before modification**, **uses sub-Agents for parallel processing during batch review, with each Agent responsible for a maximum of 3 chapters**