Run any Skill in Manus with one click

$pwd:

debug

Name: Debug
Author: cyrusagents

// Full debugging workflow — reproduce the bug with a failing test, perform root cause analysis, then implement a minimal fix.

Run Skill in Manus

$ git log --oneline --stat

stars:613

forks:121

updated:April 3, 2026 at 16:08

SKILL.md

readonly

name	debug
description	Full debugging workflow — reproduce the bug with a failing test, perform root cause analysis, then implement a minimal fix.

Debug

Debug a reported issue using a structured reproduction-then-fix approach.

Phase 1: Reproduction & Root Cause Analysis

Investigate — Analyze the bug report for key symptoms and error messages
Trace — Search the codebase for error occurrence patterns, trace from symptom to source
Root cause — Identify the root cause through data flow analysis and edge case checking
Reproduce — Create a minimal failing test case that reproduces the exact error
Document — Clearly document the root cause and reproduction steps

Phase 2: Fix Implementation

Plan — Analyze the optimal fix approach based on root cause, check for similar fixes in the codebase
Implement — Make the minimal, targeted fix that addresses the root cause
Verify — Run the failing test to confirm it passes, then run the full test suite to check for regressions

Principles

Minimal changes — Fix the bug, nothing more
Targeted — Only touch affected code paths
Tested — The fix must make the failing test pass and not break existing tests
No unrelated improvements — Stay focused on the specific bug

related-skills.json

same repository

cyrus-setup-github.md

from "cyrusagents/cyrus"

Configure GitHub for Cyrus — gh CLI login and git config for PRs, with optional webhook setup to enable @mention responses in PR comments, automated rebases and merges, and auto-fixing based on CI failures (coming soon).

2026-05-28613

cyrus-setup-slack.md

from "cyrusagents/cyrus"

Configure Slack integration for Cyrus — create a Slack app from manifest, then guide the user to save credentials.

2026-05-26613

f1-test-drive.md

from "cyrusagents/cyrus"

Orchestrate F1 test drives to validate the Cyrus agent system end-to-end across issue-tracker, EdgeWorker, and activity rendering.

2026-05-12613

release-core-test.md

from "cyrusagents/cyrus"

Invoke when dev-testing a Cyrus change that spans CYPACK (edgeworker + CLI) and CYHOST (Vercel-hosted GUI) and the hosted GUI needs to point at an unreleased `cyrus-core` from this repo. Publishes `cyrus-core` (and `claude-runner` if needed) as a `-test.N` prerelease under the npm `test` dist-tag so CYHOST can install it via `cyrus-core@test` without affecting the `latest` dist-tag or shipping a real release.

2026-05-12613

cyrus-setup-linear.md

from "cyrusagents/cyrus"

Create a Linear OAuth application and configure Cyrus to use it — supports agent-browser automation or guided manual setup.

2026-04-22613

cyrus-setup-launch.md

from "cyrusagents/cyrus"

Print a summary of the Cyrus setup and offer to start the agent.

2026-04-15613

package.json

"author": "cyrusagents"

"repository": "cyrusagents/cyrus"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	debug
description	Full debugging workflow — reproduce the bug with a failing test, perform root cause analysis, then implement a minimal fix.

Debug

Debug a reported issue using a structured reproduction-then-fix approach.

Phase 1: Reproduction & Root Cause Analysis

Investigate — Analyze the bug report for key symptoms and error messages
Trace — Search the codebase for error occurrence patterns, trace from symptom to source
Root cause — Identify the root cause through data flow analysis and edge case checking
Reproduce — Create a minimal failing test case that reproduces the exact error
Document — Clearly document the root cause and reproduction steps

Phase 2: Fix Implementation

Plan — Analyze the optimal fix approach based on root cause, check for similar fixes in the codebase
Implement — Make the minimal, targeted fix that addresses the root cause
Verify — Run the failing test to confirm it passes, then run the full test suite to check for regressions

Principles

Minimal changes — Fix the bug, nothing more
Targeted — Only touch affected code paths
Tested — The fix must make the failing test pass and not break existing tests
No unrelated improvements — Stay focused on the specific bug

debug

Debug

Phase 1: Reproduction & Root Cause Analysis

Phase 2: Fix Implementation

Principles

More from this repository

More from this repository

Debug

Phase 1: Reproduction & Root Cause Analysis

Phase 2: Fix Implementation

Principles