Loading...
Loading...
Found 12 Skills
Search for and use what already exists in libraries, runtimes, and repositories instead of building it yourself. Use this before writing new processing logic, helpers, wrappers, tools, or clients for external APIs.
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti
Applicable to code-centric tasks such as coding, debug/debugging, bug fixing, refactor/refactoring, code review, scripting, automation, and implementation planning.
Comet Preset Path: Non-bug Minor Tweaks. Skip brainstorming and full plan, directly proceed with open → lightweight build → light verify → archive. Suitable for partial optimizations of copy, configurations, documents, or prompts.
Use when anything behaves unexpectedly — a failing test, an error or exception, a crash, a reported bug, wrong output, a performance regression, a flaky CI job — and before proposing or applying any fix.
Install, manage, and search for software packages on macOS using Homebrew. Use this skill when the user asks to install software, apps, CLI tools, developer utilities, programming languages, databases, or any package on a Mac. Supports formulae (CLI tools) and casks (GUI apps). Can also search, update, upgrade, uninstall, and diagnose Homebrew issues.
Fix confirmed bugs from user reports, runtime failures, failing tests, or verified `/find-bugs` findings. Reproduce the bug first, diagnose the real root cause, apply the smallest correct fix, verify against regressions, and report exactly what changed. Loads framework-specific references and category-specific playbooks as needed. Use when the user says "fix this bug", "fix the findings", "/bugfix", or asks to repair a confirmed defect.
Generate a Software Maintenance Plan (SMP) and supporting maintenance documentation for SDLC projects. Compliant with ISO/IEC/IEEE 14764:2022. Covers Maintenance Strategy, MR/PR handling workflow, CCB process, maintenance cost estimation, and all...
Use when restructuring existing code without changing observable behavior, especially when a feature or bug fix is hard because the current design is awkward, duplicated, confusing, or risky to modify.
Phase 2 of the issue process — Read the issue report + read the code, identify the true root cause and assess the repair risk, and finally provide the user with 2-3 repair plan options for them to decide. This phase is **not about starting to modify code** — after analysis, show the conclusion to the user first, and only proceed to Phase 3 after the user confirms the plan. The prerequisite dependency easysdd-issue-report has been completed. Trigger scenarios: The user says "analyze this bug", "find the root cause", "locate the issue", and the {slug}-report.md already exists in the issue directory.
Gut-check a pull request — is it meaningful, worth adding, correct, and minimal — and give one recommend-* verdict.
Refactor fat controllers into lean ones by extracting business logic to services, handlers, and invokable commands