Run any Skill in Manus with one click

bug-fix

Stars25

Forks3

UpdatedMarch 28, 2026 at 18:11

Diagnose and fix implementation errors from stack traces, identify root cause, apply minimum effective fixes, and validate with lint/format/build/test loops until green. Use for debugging and defect resolution tasks.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

posaune0423

posaune0423/mdv

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	bug-fix
description	Diagnose and fix implementation errors from stack traces, identify root cause, apply minimum effective fixes, and validate with lint/format/build/test loops until green. Use for debugging and defect resolution tasks.

Bug Fix

Steps

Read the error and stack trace carefully, then inspect the related files and code to identify a concrete root cause.
If root cause cannot be identified because required information is missing, report exactly what is missing to the developer.
Choose the minimum but effective method to solve that root cause.
Apply the fix.
Run lint, format, build, and test (when available), then verify all tests pass.
If tests fail, use the new failure as input and restart this flow from step 1.

More from this repository

same repository

code-review

posaune0423/mdv

AI-powered code review using CodeRabbit. Default code-review skill. Trigger for any explicit review request AND autonomously when the agent thinks a review is needed (code/PR/quality/security).

2026-03-2825

create-pr

posaune0423/mdv

Create or update a PR from current branch to main, watch CI, and address feedback

2026-03-2825

final-check

posaune0423/mdv

Run final quality gates (lint, format, typecheck), fix root causes with minimal changes, and repeat until no errors or warnings remain. Use before completion or handoff.

2026-03-2825

test-driven-development

posaune0423/mdv

Use when implementing any feature or bugfix, before writing implementation code

2026-03-2825

update-pr

posaune0423/mdv

Update an existing pull request with new changes or respond to review feedback. Use when addressing PR comments, making requested changes, or updating a PR after review.

2026-03-2825

name	bug-fix
description	Diagnose and fix implementation errors from stack traces, identify root cause, apply minimum effective fixes, and validate with lint/format/build/test loops until green. Use for debugging and defect resolution tasks.

Bug Fix

Steps

Read the error and stack trace carefully, then inspect the related files and code to identify a concrete root cause.
If root cause cannot be identified because required information is missing, report exactly what is missing to the developer.
Choose the minimum but effective method to solve that root cause.
Apply the fix.
Run lint, format, build, and test (when available), then verify all tests pass.
If tests fail, use the new failure as input and restart this flow from step 1.