Run any Skill in Manus with one click

debugging

Stars87

Forks16

UpdatedApril 12, 2026 at 18:34

Systematic debugging of issues — use when a test fails, runtime error occurs, unexpected behavior is reported, or an awareness tick produces anomalous results

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

WingedGuardian

WingedGuardian/GENesis-AGI

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	debugging
description	Systematic debugging of issues — use when a test fails, runtime error occurs, unexpected behavior is reported, or an awareness tick produces anomalous results
consumer	cc_background_task
phase	6
skill_type	workflow

Debugging

Purpose

Systematically diagnose and resolve bugs, failures, or unexpected behavior in Genesis or its dependencies.

When to Use

A test fails unexpectedly.
Runtime error or unexpected behavior is reported.
An awareness tick or reflection produces anomalous results.
Obstacle resolution escalates a technical issue.

Workflow

Reproduce — Confirm the issue. Get the exact error, stack trace, or unexpected output. Define "expected vs. actual."
Isolate — Narrow the scope. Which module? Which function? Which input triggers it? Use binary search on the call chain.
Hypothesize — Form 2-3 candidate explanations. Rank by likelihood.
Test hypotheses — Write a minimal test or add logging to confirm/deny each hypothesis. Start with the most likely.
Fix — Apply the minimal correct fix. Do not fix adjacent issues in the same change.
Verify — Run the failing test. Run the full test suite. Confirm no regressions.
Document — Record the root cause and fix as an observation. Update procedures if the bug class is recurring.

Output Format

issue: <one-line description>
date: <YYYY-MM-DD>
root_cause: <what actually went wrong>
fix: <what was changed>
files_modified:
  - <file path>
regression_risk: low | medium | high
lesson: <what to remember to prevent recurrence>

Examples

Example: Hook fails in non-login shell

Trigger: Post-commit hook throws KeyError: 'HOME' in CI-like environment.

Expected output:

issue: Post-commit hook crashes when HOME not set in non-login sessions
date: 2026-04-06
root_cause: Hook script reads os.environ["HOME"] but non-login shells
  (systemd, cron) strip HOME from environment
fix: Guard with os.environ.get("HOME", "/root") fallback + persist HOME
  in /etc/environment during install
files_modified:
  - .claude/hooks/genesis-hook
  - scripts/install_guardian.sh
regression_risk: low
lesson: Never assume HOME exists — non-login shells strip it. Always
  use get() with fallback for environment variables in hook scripts.

References

tests/ — Test suite for verification
src/genesis/learning/procedural/ — Procedure updates for recurring patterns

More from this repository

same repository

genesis-development

WingedGuardian/GENesis-AGI

This skill should be used when developing, debugging, refactoring, or building Genesis itself — tasks like "fix this in Genesis", "add a new MCP tool", "wire up the runtime", "Genesis won't start", "create a worktree", "debug the bridge", or "add a capability". Applies to any task modifying files under src/, .claude/, or tests/. Do NOT load for Genesis-as-tool work ("summarize this", "write a LinkedIn post", "research X") or general questions unrelated to Genesis internals.

2026-07-1889

voice-master

WingedGuardian/GENesis-AGI

Foundational voice authority and AI humanizer — writes content in the user's authentic voice with built-in AI detection, and supports stealth / anti- attribution writing (forum personas, anonymous posts, "write as not-me"). Use when asked to write/draft/generate content, invoke /voice, /write-as-me, or /humanize, run voice calibration, check "does this sound like me?", "make this sound human" / "de-AI this", "write a forum post as [persona]", or run AI detection ("does this sound like AI?", "check for AI patterns", "anti-slop check"). Do NOT use this skill for code, technical docs, or any output the user has not asked to be written in their voice — code styling defers to the separate code-voice skill.

2026-07-1489

aws-fde-delivery

WingedGuardian/GENesis-AGI

Forward Deployed Engineer delivery contract for AWS engagements, build-first artifacts, grounded cost estimates, Well-Architected review, evolution roadmap

2026-07-0789

subsystem-map

WingedGuardian/GENesis-AGI

This skill should be used before answering "does Genesis have X", "does Genesis lack X", auditing Genesis capabilities, comparing Genesis to an external system, or reviewing/summarizing the architecture. It routes to the canonical judgment-layer subsystem map so audits start from the map, not from a cold grep. Also fires after changing a subsystem's capabilities, to keep the map current.

2026-07-0789

onboarding

WingedGuardian/GENesis-AGI

First-run onboarding — guides new users through Genesis setup on their first CC session. Configures user profile, essential API keys, Telegram, GitHub backup, and service verification. Triggered automatically when ~/.genesis/setup-complete is absent. Re-runnable by asking Genesis to "run setup" or "reconfigure [section]".

2026-07-0689

genesis-voice

WingedGuardian/GENesis-AGI

Apply when Genesis writes as itself — outreach, public content, community posts, emails, DMs. Not for writing in the user's voice (that's voice-master). Activate when Genesis is the author, not the ghostwriter.

2026-07-0489

Debugging

Purpose

Systematically diagnose and resolve bugs, failures, or unexpected behavior in Genesis or its dependencies.

When to Use

A test fails unexpectedly.

Runtime error or unexpected behavior is reported.

An awareness tick or reflection produces anomalous results.

Obstacle resolution escalates a technical issue.

Workflow

Reproduce — Confirm the issue. Get the exact error, stack trace, or unexpected output. Define "expected vs. actual."

Isolate — Narrow the scope. Which module? Which function? Which input triggers it? Use binary search on the call chain.

Hypothesize — Form 2-3 candidate explanations. Rank by likelihood.

Test hypotheses — Write a minimal test or add logging to confirm/deny each hypothesis. Start with the most likely.

Fix — Apply the minimal correct fix. Do not fix adjacent issues in the same change.

Verify — Run the failing test. Run the full test suite. Confirm no regressions.

Document — Record the root cause and fix as an observation. Update procedures if the bug class is recurring.

Output Format

issue: <one-line description> date: <YYYY-MM-DD> root_cause: <what actually went wrong> fix: <what was changed> files_modified: - <file path> regression_risk: low | medium | high lesson: <what to remember to prevent recurrence>

Examples

Example: Hook fails in non-login shell

Trigger: Post-commit hook throws KeyError: 'HOME' in CI-like environment.

Expected output:

issue: Post-commit hook crashes when HOME not set in non-login sessions date: 2026-04-06 root_cause: Hook script reads os.environ["HOME"] but non-login shells (systemd, cron) strip HOME from environment fix: Guard with os.environ.get("HOME", "/root") fallback + persist HOME in /etc/environment during install files_modified: - .claude/hooks/genesis-hook - scripts/install_guardian.sh regression_risk: low lesson: Never assume HOME exists — non-login shells strip it. Always use get() with fallback for environment variables in hook scripts.

References

tests/ — Test suite for verification

src/genesis/learning/procedural/ — Procedure updates for recurring patterns