ワンクリックでManusで任意のスキルを実行

bug-fix-iteration

スター17

フォーク1

更新日2026年3月5日 15:35

Systematic approach to fixing bugs reported via pasted logs. Prevents the agent from making broad changes that introduce regressions when only a targeted fix is needed. [GENERATED BY MOTIF — review and customize]

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

Bulugulu

Bulugulu/motif-cli

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Bug Fix Iteration

Systematic approach to fixing bugs reported via pasted logs. Prevents the agent from making broad changes that introduce regressions when only a targeted fix is needed.

When to Use

User pastes error logs, stack traces, or console output
User says 'it's still broken' or 'that didn't work'
Especially when: previous fix attempt didn't resolve the issue
Don't skip when: the error seems 'obvious' -- still follow the process

Instructions

Read the pasted logs carefully
- identify the exact error message and location
If error is ambiguous, ask the user one clarifying question before proceeding
Check if this is a known issue pattern (same file/component as previous bugs)
Propose a targeted fix that addresses only the specific error
Do NOT refactor or modify unrelated code in the same change
Apply the fix
Ask user to test and report back
If fix doesn't work after 2 attempts, step back and investigate root cause more broadly

Best Practices

Read the entire error message, not just the first line
Fix one thing at a time -- don't bundle multiple changes
Avoid: Don't refactor code that isn't related to the bug
Always ask the user to verify the fix worked

Common Pitfalls

Problem	Solution
Agent modifies unrelated code, causing new bugs	Only touch files directly related to the reported error
Agent proposes sweeping refactor instead of targeted fix	Fix the bug first; propose refactoring separately if needed
Going in circles with the same fix approach	After 2 failed attempts, investigate root cause from a different angle

Key Constraints

Never modify files unrelated to the reported bug
Always ask the user to verify after applying a fix
After 2 failed fix attempts, change your investigation approach

このリポジトリの他の Skills

同じリポジトリ

motif-analyze

Bulugulu/motif-cli

Run Motif — your AI coding companion. Use when the user mentions "motif" in any context. Covers vibe reports, live dashboard, and AI personalization.

2026-03-1517

motif-analyze

Bulugulu/motif-cli

Run Motif — your AI coding companion. Use when the user mentions "motif" in any context. Covers vibe reports, live dashboard, and AI personalization.

2026-03-1517

motif-analyze

Bulugulu/motif-cli

Run Motif to generate your vibe report, launch the live dashboard, or personalize your CLAUDE.md and skills. Use when the user says "motif", "run motif", "vibe report", "generate my report", "motif live", "start the dashboard", "analyze my coding patterns", "personalize my AI", "generate rules for me", or "motif analyze".

2026-03-1417

deploy-production

Bulugulu/motif-cli

Standardized deployment workflow for this specific project's infrastructure. Prevents deployment failures from skipped steps or wrong order. [GENERATED BY MOTIF — review and customize]

2026-03-0517

unity-tool-creation

Bulugulu/motif-cli

Workflow for creating Unity tools and features that can be tested in isolation. Prevents untestable features in a multiplayer context. [GENERATED BY MOTIF — review and customize]

2026-03-0517

session-startup

Bulugulu/motif-cli

Ensures the agent is oriented on the current project state before taking action. Prevents the agent from working with stale context or making assumptions about project status. [GENERATED BY MOTIF — review and customize]

2026-03-0517

name	bug-fix-iteration
description	Systematic approach to fixing bugs reported via pasted logs. Prevents the agent from making broad changes that introduce regressions when only a targeted fix is needed. [GENERATED BY MOTIF — review and customize]

Bug Fix Iteration

Systematic approach to fixing bugs reported via pasted logs. Prevents the agent from making broad changes that introduce regressions when only a targeted fix is needed.

When to Use

User pastes error logs, stack traces, or console output
User says 'it's still broken' or 'that didn't work'
Especially when: previous fix attempt didn't resolve the issue
Don't skip when: the error seems 'obvious' -- still follow the process

Instructions

Read the pasted logs carefully
- identify the exact error message and location
If error is ambiguous, ask the user one clarifying question before proceeding
Check if this is a known issue pattern (same file/component as previous bugs)
Propose a targeted fix that addresses only the specific error
Do NOT refactor or modify unrelated code in the same change
Apply the fix
Ask user to test and report back
If fix doesn't work after 2 attempts, step back and investigate root cause more broadly

Best Practices

Read the entire error message, not just the first line
Fix one thing at a time -- don't bundle multiple changes
Avoid: Don't refactor code that isn't related to the bug
Always ask the user to verify the fix worked

Common Pitfalls

Problem	Solution
Agent modifies unrelated code, causing new bugs	Only touch files directly related to the reported error
Agent proposes sweeping refactor instead of targeted fix	Fix the bug first; propose refactoring separately if needed
Going in circles with the same fix approach	After 2 failed attempts, investigate root cause from a different angle

Key Constraints

Never modify files unrelated to the reported bug
Always ask the user to verify after applying a fix
After 2 failed fix attempts, change your investigation approach