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

fix-bug

スター27

フォーク5

更新日2026年5月20日 22:48

This skill should be used when the user asks to "fix bug", "resolve issue", "fix error", "troubleshoot", "debug", or reports a specific bug or error that needs investigation and fixing.

インストール

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

Manusで実行

ソース

nrjdalal

nrjdalal/awesome-templates

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

ダウンロード

Manusで実行

Bug Fix Workflow

Bug description: $ARGUMENTS

Default Flow Position

4-phase 1:1 mapping: Reproduce → framing, Trace → plan, Fix → implement, Verify → verify
approach options upstream conditional — required if multiple layer-fix candidates or missing pattern
Routes after: self-review (/review-architecture if layer interactions changed; /security-review if security-relevant) → completion gate (/review-pr)
[hotfix] / [긴급] exception is the natural escape for time-critical fixes; verify still mandatory
Recursion guard: do not invoke /fix-bug recursively. Do not invoke /plan-feature from inside

Procedure Overview

Reproduce — identify affected domain/layer, write failing test (Phase 1)
Trace — follow call path, inspect conversion boundaries and DI wiring (Phase 2)
Fix — fix at lowest layer, follow existing patterns (Phase 3)
Verify — confirm test passes, run domain tests and pre-commit (Phase 4)
Commit — propose conventional commit message (Phase 5)

Read docs/ai/shared/skills/fix-bug.md for detailed steps. Also refer to docs/ai/shared/project-dna.md §6 for conversion patterns and §9 for router patterns.

このリポジトリの他の Skills

同じリポジトリ

sync-guidelines

nrjdalal/awesome-templates

Inspect drift between code, shared workflow references, and Claude, Codex, or Antigravity harness assets after architecture or workflow changes.

2026-07-1427

sync-guidelines

nrjdalal/awesome-templates

This skill should be used when the user asks to "sync guidelines", "document inspection", "check skill updates", "update project-dna", "sync patterns", "verify code-document consistency", or after architecture changes to verify Skills/AGENTS.md/CLAUDE.md match the actual code.

2026-07-1427

plan-feature

nrjdalal/awesome-templates

Guide a feature from requirements interview through architecture analysis, security check, and task decomposition.

2026-07-0927

plan-feature

nrjdalal/awesome-templates

This skill should be used when the user asks to "plan feature", "design feature", or wants to plan and design a new feature before implementation.

2026-07-0927

review-architecture

nrjdalal/awesome-templates

Audit a domain or the full repository for architecture compliance using the shared architecture checklist and repository rules.

2026-07-0427

review-pr

nrjdalal/awesome-templates

Review a pull request or local diff against the repository's shared Review Protocol (correctness, regression, stability, contract, architecture, security, governance).

2026-07-0427

name	fix-bug
argument-hint	bug description or issue number
description	This skill should be used when the user asks to "fix bug", "resolve issue", "fix error", "troubleshoot", "debug", or reports a specific bug or error that needs investigation and fixing.

Bug Fix Workflow

Bug description: $ARGUMENTS

Default Flow Position

4-phase 1:1 mapping: Reproduce → framing, Trace → plan, Fix → implement, Verify → verify
approach options upstream conditional — required if multiple layer-fix candidates or missing pattern
Routes after: self-review (/review-architecture if layer interactions changed; /security-review if security-relevant) → completion gate (/review-pr)
[hotfix] / [긴급] exception is the natural escape for time-critical fixes; verify still mandatory
Recursion guard: do not invoke /fix-bug recursively. Do not invoke /plan-feature from inside

Procedure Overview

Reproduce — identify affected domain/layer, write failing test (Phase 1)
Trace — follow call path, inspect conversion boundaries and DI wiring (Phase 2)
Fix — fix at lowest layer, follow existing patterns (Phase 3)
Verify — confirm test passes, run domain tests and pre-commit (Phase 4)
Commit — propose conventional commit message (Phase 5)

Read docs/ai/shared/skills/fix-bug.md for detailed steps. Also refer to docs/ai/shared/project-dna.md §6 for conversion patterns and §9 for router patterns.