Source profileQuality 92/100

WingedGuardian/GENesis-AGI/src/genesis/skills/debugging/SKILL.md

debugging

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

Source repository stars
90
Declared platforms
0
Static risk flags
0
Last source update
2026-08-25
Source checked
2026-08-25

Decision brief

What it does: where it fits

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

Best for

  • A test fails unexpectedly.
  • Runtime error or unexpected behavior is reported.
  • An awareness tick or reflection produces anomalous results.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/WingedGuardian/GENesis-AGI --skill "src/genesis/skills/debugging"
Safe inspection promptEditorial

Inspect the Agent Skill "debugging" from https://github.com/WingedGuardian/GENesis-AGI/blob/41b61096364a53a8000b2ef4020c25cee9cfeec2/src/genesis/skills/debugging/SKILL.md at commit 41b61096364a53a8000b2ef4020c25cee9cfeec2. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

    1. Reproduce — Confirm the issue. Get the exact error, stack trace, or unexpected output. Define "expected vs. actual." 2. Isolate — Narrow the scope. Which module? Which function? Which input triggers it? Use binary search on the call chain. 3. Hypothesize — Form 2-3 candidate…

    Reproduce — Confirm the issue. Get the exact error, stack trace, orIsolate — Narrow the scope. Which module? Which function? Which inputHypothesize — Form 2-3 candidate explanations. Rank by likelihood.
  2. 02

    Purpose

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

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

    When to Use

    A test fails unexpectedly.

    A test fails unexpectedly.Runtime error or unexpected behavior is reported.An awareness tick or reflection produces anomalous results.
  4. 04

    Output Format

    Review the “Output Format” section in the pinned source before continuing.

    Review and apply the “Output Format” source section.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score92/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars90SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
WingedGuardian/GENesis-AGI
Skill path
src/genesis/skills/debugging/SKILL.md
Commit
41b61096364a53a8000b2ef4020c25cee9cfeec2
License
MIT
Collected
2026-08-25
Default branch
main
View the original SKILL.md

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

  1. Reproduce — Confirm the issue. Get the exact error, stack trace, or unexpected output. Define "expected vs. actual."
  2. Isolate — Narrow the scope. Which module? Which function? Which input triggers it? Use binary search on the call chain.
  3. Hypothesize — Form 2-3 candidate explanations. Rank by likelihood.
  4. Test hypotheses — Write a minimal test or add logging to confirm/deny each hypothesis. Start with the most likely.
  5. Fix — Apply the minimal correct fix. Do not fix adjacent issues in the same change.
  6. Verify — Run the failing test. Run the full test suite. Confirm no regressions.
  7. 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

Frequently asked questions

What to verify before installation and use

What does the debugging source document cover?

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

How do I install debugging?

The source record exposes this install command: npx skills add https://github.com/WingedGuardian/GENesis-AGI --skill "src/genesis/skills/debugging". Inspect the command and pinned source before running it.

Alternatives

Compare before choosing

Computed 10029,034

garrytan/gbrain

bulk-ingestion

End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.

Computed 10024,921

alirezarezvani/claude-skills

app-store-optimization

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

Computed 1005,241

dotnet/skills

migrate-vstest-to-mtp

Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP). Use when user asks to "migrate to MTP", "switch from VSTest", "enable Microsoft.Testing.Platform", "use MTP runner", set OutputType=Exe only for test projects in Directory.Build.props, or mentions EnableMSTestRunner, EnableNUnitRunner, or UseMicrosoftTestingPlatformRunner. USE FOR: MTP behavioral differences vs VSTest (exit code 8, zero tests discovered, --ignore-exit-code, TESTINGPLATFORM_EXITCODE_IGNORE); centralizing

Computed 991,257

vipshop/cache-dit

cache-dit-model-integration

High-level guide for integrating a new DiT model into cache-dit: Cache (BlockAdapter/ForwardPattern), Context Parallelism, Tensor Parallelism, Text Encoder Parallelism (TE-P), VAE Parallelism (VAE-P), generate CLI, installation, testing workflow, and detailed references. Use when adding support for a new diffusion transformer model in cache-dit.