debugging-workflows
Diagnose gh-aw failures using the canonical debugging strategy and evidence reference.
- Installs
- 67
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/github/gh-aw --skill debugging-workflows- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads debugging-workflows automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Workflow Debugging Router
This skill remains available for existing invocations. Load and follow the evidence reference, where the instructions now live. It delegates setup to the bootstrap and execution policy to the shared strategy.
Use a matching local guidance checkout. For Contents API reads, use the guidance
owner/repository (owner=github, repo=gh-aw by default),
path=.github/aw/debug-workflow-evidence.md, retaining the ref of this skill.
The other API paths are .github/aw/debug-bootstrap.md and
.github/aw/debug-agentic-workflow.md. Normalize relative links against their
containing file before API reads; ../../aw/... is not an API path.
For default raw guidance, use https://raw.githubusercontent.com/github/gh-aw/<guidance-ref>/
plus the repository-root-relative path, including .github/. Preserve supplied
refs containing slashes and keep guidance identity separate from the target
workflow repository/ref. The bootstrap documents size-aware reads and public
raw fallback after API denial.
Read the canonical instructions before running commands. This compatibility router defines no separate setup, review, or live-execution procedure.
FAQ
What does the debugging-workflows skill do?
Diagnose gh-aw failures using the canonical debugging strategy and evidence reference.
How do I install debugging-workflows?
Run npx skills add https://github.com/github/gh-aw --skill debugging-workflows in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/debugging-workflows/ (personal) or .claude/skills/debugging-workflows/ (project).
Which AI agents can use debugging-workflows?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is debugging-workflows safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains debugging-workflows?
It is published by github in github/gh-aw, and it is an official skill from the maker of the technology it covers. It has 67 recorded installs.
More from github/gh-aw
github-mcp-server
github/gh-aw
Open the skill to read its SKILL.md instructions.
developer
github/gh-aw
Core developer rules and coding conventions for gh-aw changes.
javascript-refactoring
github/gh-aw
Split large JavaScript files into maintainable modules safely.
agentic-workflows
github/gh-aw
Open the skill to read its SKILL.md instructions.
github-pr-query
github/gh-aw
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.