メニュー
Debug and fix broken code. Use when errors occur, tests fail, or the application isn't working as expected. Performs root cause analysis, implements fixes, adds regression tests, and documents the bug.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Kibbey/fyli --skill fixerコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Audit the codebase for dead code, duplicate code, inefficient code, overloaded code, missing test coverage, non-conforming code, stale documentation, and other best practice violations. Uses parallel subagents for discovery and hands off findings to /architect to create a TDD for fixes.
Review code for quality, standards compliance, and best practices. Use when asked to review code, check for issues, audit code quality, or validate implementations against project standards.
Design and plan software architecture for new features or refactoring. Use when asked to architect a solution, design a feature, create TDD, plan implementation, or make architectural decisions.
SKILL.md を表示中
SOC 職業分類に基づく
| name | fixer |
| description | Debug and fix broken code. Use when errors occur, tests fail, or the application isn't working as expected. Performs root cause analysis, implements fixes, adds regression tests, and documents the bug. |
| allowed-tools | Read, Grep, Glob, Task, Edit, Write, Bash, Skill |
Systematically debug issues, implement fixes, and document bugs to prevent recurrence.
Check error logs in order of priority:
docs/issue.md - User-reported issues if logs are emptyIdentify the error pattern:
Check if this is a known bug - Review common_bugs.md for similar errors
Information Gathering Checklist:
[ ] Read error.log for recent errors
[ ] Identify the error message and stack trace
[ ] Note the file(s) and line number(s) involved
[ ] Check common_bugs.md for existing documentation
[ ] Understand what user action triggered the error
Common root causes to check:
Fix Implementation Checklist:
[ ] Root cause identified and understood
[ ] Fix addresses the root cause (not just symptom)
[ ] Changes follow existing code patterns
[ ] Edge cases considered and handled
[ ] No new security vulnerabilities introduced
Add regression tests to prevent the bug from recurring:
# Run backend tests to verify fix
cd cimplur-core/Memento && dotnet test
# Run frontend tests to verify fix
cd fyli-fe-v2 && npm run test:unit -- --run
Full testing standards: See
docs/TESTING_BEST_PRACTICES.mdfor detailed patterns and examples.
Update common_bugs.md following the established format:
If this is a NEW bug type, add a new section:
## [N]. [Brief Bug Title]
**Count:** 1
**Error Message:**
[Exact error message from logs]
**Root Cause:**
[Clear explanation of why this happened]
**Location:**
- `[file-path]` - `[method-name]` (line X)
**Fix:**
[Description and code example of the fix]
**Prevention:**
- [How to avoid this in the future]
- [What patterns to follow]
If this bug already exists, increment the Count field only.
Run the designer skill (if frontend changes were made):
/designer
Make changes based on feedback to ensure design compliance.
Run the code-review skill:
/code-review
Address any critical issues or improvements identified.
Clear logs and restart the server to verify the fix:
dotnet run
This restarts the application to verify the fix works.
{
"level": "error",
"message": "Error description",
"stack": "Error: ...\n at functionName (file:line:col)",
"method": "POST",
"url": "/api/endpoint",
"statusCode": 500,
"timestamp": "2026-01-24 10:00:00"
}
Key fields to examine:
message - What went wrongstack - Where it happened (read bottom-to-top for call chain)url - Which endpoint was calledstatusCode - HTTP response code| Error Type | Typical Cause | Where to Look |
|---|---|---|
foreign key constraint | FK references wrong/missing table | Migrations, schema |
column does not exist | Query uses non-existent column | Repository, DATA_SCHEMA.md |
invalid input syntax | Bad data format (dates, UUIDs) | Service layer, input validation |
ECONNREFUSED | Database/service not running | Docker, connection config |
NullReferenceException | Null access | Add null checks |
Before marking the fix complete:
[ ] Root cause identified and documented
[ ] Fix implemented and tested locally
[ ] Regression test added (if applicable)
[ ] common_bugs.md updated
[ ] All tests passing
[ ] Code review completed (via /code-review)
[ ] Designer review completed (if frontend changes)
[ ] Server restarted with dotnet run
[ ] Verified fix works in running application
When reporting a fix, provide:
## Bug Fix Summary
**Error:** [Brief description]
**Root Cause:** [Why it happened]
**Fix:** [What was changed]
**Files Modified:**
- [File1.cs] - [what changed]
- [File2.cs] - [what changed]
**Tests Added:**
- [TestFile.cs] - [what it tests]
**Verified:** [How you confirmed the fix works]