Saucebox Registry
← Browse

@majiayu000/debugging-checklist

B

Provide a systematic debugging checklist. Use when a junior developer is stuck and needs a structured approach.

skillclaude

Install

agr install @majiayu000/debugging-checklist --target claude

Writes 2 files into .claude/skills/, pinned to git-c3ff7ce9.

  • .claude/skills/debugging-checklist/SKILL.md
  • .claude/skills/debugging-checklist/metadata.json

Document

name: debugging-checklist description: Provide a systematic debugging checklist. Use when a junior developer is stuck and needs a structured approach.

Debugging Checklist

Purpose

Provide a systematic debugging checklist.

Inputs to request

  • Repro steps and frequency.
  • Environment details and recent changes.
  • Logs, stack traces, or screenshots.

Workflow

  1. Reproduce the issue and isolate the scope.
  2. Check inputs, environment, and recent changes.
  3. Add targeted logs or breakpoints.

Output

  • Checklist ordered by likelihood.

Quality bar

  • Start with reversible, low-risk checks.
  • Prefer minimal probes over broad logging.

Repository README

Describes majiayu000/claude-skill-registry-data as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.

Claude Skill Registry (Data)

This repo contains the archived skill contents (the heavy, browsable skill files).

Canonical layout

  • Category folders at repo root (e.g. development/, documents/, data/, ...)
  • Each skill lives under a category: <category>/<skill>/SKILL.md + <category>/<skill>/metadata.json
  • Case conflicts are resolved with {name}-{owner}-{repo} suffixes (fallback: -{short-hash}).

Archive status

  • Live badges above are sourced from claude-skill-registry-core stats.json.
  • Counts in this README are intentionally dynamic, not hardcoded.
  • If the badges look stale, refresh the core build/index pipeline rather than editing numbers here.

Where the index + site live

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-c3ff7ce9d7c52026-07-31