Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

debug

Sterne2

Forks0

Aktualisiert13. März 2026 um 00:34

This skill should be used when the user asks to "debug this", "fix this bug", "find the root cause", "investigate an error", "troubleshoot", "why is this failing", "trace the issue", or mentions errors, exceptions, stack traces, or unexpected behavior that needs investigation. Launches the debugger agent for systematic root cause analysis.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

Conava

Conava/claude-devline

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

Mehr aus diesem Repository

gleiches Repository

kb-blast-radius

Conava/claude-devline

Grep-based reverse dependency analysis — injected into planner, reviewer, and deep-review agents. Computes which files are affected by changes to a set of seed files. Not invoked directly.

2026-04-092

brainstorm

Conava/claude-devline

This skill should be used when the user asks to "brainstorm", "refine an idea", "flesh out a feature", "define requirements". Guides interactive refinement of rough ideas into concise, actionable feature specifications. Focuses on the "what" and architecture — never the "how".

2026-04-092

devline

Conava/claude-devline

This is the default skill for all development work. It orchestrates the entire development lifecycle from idea to merge-ready code, coordinating multiple agents for brainstorming, planning, implementation, review, documentation, and final approval. Use this for any development task that is non-trivial and could benefit from structured planning, parallel execution, and rigorous review or require more than 3 lines of code changed.

2026-04-092

find-docs

Conava/claude-devline

Retrieves authoritative, up-to-date technical documentation, API references, configuration details, and code examples for any developer technology. Use this skill whenever answering technical questions or writing code that interacts with external technologies. This includes libraries, frameworks, programming languages, SDKs, APIs, CLI tools, cloud services, infrastructure tools, and developer platforms. Common scenarios: - looking up API endpoints, classes, functions, or method parameters - checking configuration options or CLI commands - answering "how do I" technical questions - generating code that uses a specific library or service - debugging issues related to frameworks, SDKs, or APIs - retrieving setup instructions, examples, or migration guides - verifying version-specific behavior or breaking changes Prefer this skill whenever documentation accuracy matters or when model knowledge may be outdated.

2026-04-092

implement

Conava/claude-devline

Implement tasks using TDD. Accepts a plan or specific task description. Runs implementer agents in parallel where possible.

2026-04-092

kb-design

Conava/claude-devline

Design intelligence for UI/UX — injected into the frontend-planner agent. Provides BM25-searchable database of 67 styles, 161 color palettes, 57 font pairings, 160 animated component patterns, 161 industry rules, plus framework-agnostic design guidelines. Not invoked directly.

2026-04-092

name	debug
description	This skill should be used when the user asks to "debug this", "fix this bug", "find the root cause", "investigate an error", "troubleshoot", "why is this failing", "trace the issue", or mentions errors, exceptions, stack traces, or unexpected behavior that needs investigation. Launches the debugger agent for systematic root cause analysis.
argument-hint	<bug description, error message, or failing test>
user-invocable	true
disable-model-invocation	false

Debug — Systematic Bug Investigation

Launch the debugger agent to investigate and fix a bug using systematic root cause analysis.

Determine Scope

If the user provides an error message, stack trace, or failing test — pass it directly
If the user describes unexpected behavior — pass the description
If no specifics given, the debugger will reproduce the issue first

After Debug

Present the debugger's findings:

Root cause identified and fixed
Or: root cause identified, fix needs user decision

If the fix touches multiple files or is complex, suggest running /devline:review on the changes.