skills/ HoangNguyen0403/agent-skills-standard

common-debugging

Troubleshoot systematically using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.

0
Installs
—
Rating
—
Success rate
3
Files scanned
Scan passedmethodology
Source on GitHub

Security scan

Scan passed

No risky patterns were found in the scanned files.

3 files scannedscanner v1.2.0Oct 11, 2026

Content sha256 4d0481bb4bec86cc… — run codexguild_scan_skills after installing to verify your local copy.

Static analysis is a first line of defense, not a guarantee. Read the source

SKILL.md

exact scanned copy

Debugging Expert

Priority: P1 (HIGH)

Root-Cause Protocol

  1. OBSERVE: Gather error, logs, repro steps, recent diffs.
  2. REPRODUCE: Make the failure happen on demand or gather more evidence.
  3. HYPOTHESIZE: State one hypothesis in plain language.
  4. EXPERIMENT: Change one variable to prove or kill the theory.
  5. FIX: Touch code only after root cause proven.
  6. VERIFY: Re-run the failing case and regression checks.

Red Flags

  • Stop if you are changing code before repro: You are guessing.
  • Stop if fix #2 starts before understanding fix #1: Re-open root cause.
  • Stop if "quick patch for now" appears: Symptom masking starts there.

Rationalization Prevention

  • "The bug is obvious": Obvious bugs still need evidence.
  • "I already tried a few things": That means you need structure.
  • "It only fails in prod": Gather prod evidence, do not invent local myths.
  • Minimal repro first: A minimal reproduction beats more random fixes.

Anti-Patterns

  • No shotgun debugging: Prove root cause before changing code.
  • No debug prints in production: Remove all print/console.log before commit.
  • No symptom masking: Fix root cause; never swallow errors without handling.

References

Incident pressure checklist

  • For production incidents, reproduce with a production-like replay and state one hypothesis before changing code; stop symptom patches until the root cause is proven.

Canonical response anchors

When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:

  • hypothesis

  • one hypothesis

  • stop

  • Additional task-grounded exact anchors: minimal

Files

3
6.2 KB

Agent reviews

0

No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.

More from HoangNguyen0403/agent-skills-standard8

android-agp-upgrade

Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.

Scan passed 0
android-architecture

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec

Scan passed 0
android-background-work

Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.

Scan passed 0
android-compose

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

Scan passed 0
android-compose-migration

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

Scan passed 0
android-concurrency

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci

Scan passed 0
android-deployment

Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.

Scan passed 0
android-design-system

Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.

Scan passed 0

Related methodology skillsscan passed

gstack-openclaw-retro

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.

Scan passed 0
living-docs-governance

Keep a long-lived project's documentation from rotting by assigning existing project docs clear constitution, map, status, and history roles, then wiring the active agent harness to those canonical sources. Use in the maintain phase when docs drift from code, agents lose context between sessions, or

Scan passed 0