OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
Four-phase root cause investigation for bugs and unexpected behavior
Install Systematic Debugging
$ npx skills add taracodlabs/aiden --skill systematic-debugging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install taracodlabs/aiden systematic-debugging --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/taracodlabs/aiden.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/systematic-debugging .claude/skills/systematic-debugging && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "systematic-debugging" agent skill from https://github.com/taracodlabs/aiden/tree/main/skills/systematic-debugging into .claude/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/taracodlabs/aiden/tree/main/skills/systematic-debuggingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add taracodlabs/aiden --skill systematic-debugging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install taracodlabs/aiden systematic-debugging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/taracodlabs/aiden.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/systematic-debugging .agents/skills/systematic-debugging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "systematic-debugging" agent skill from https://github.com/taracodlabs/aiden/tree/main/skills/systematic-debugging into .agents/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add taracodlabs/aiden --skill systematic-debugging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install taracodlabs/aiden systematic-debugging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/taracodlabs/aiden.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/systematic-debugging .cursor/skills/systematic-debugging && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "systematic-debugging" agent skill from https://github.com/taracodlabs/aiden/tree/main/skills/systematic-debugging into .cursor/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/taracodlabs/aiden.git --path skills/systematic-debugging--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add taracodlabs/aiden --skill systematic-debugging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install taracodlabs/aiden systematic-debugging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/taracodlabs/aiden.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/systematic-debugging .gemini/skills/systematic-debugging && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "systematic-debugging" agent skill from https://github.com/taracodlabs/aiden/tree/main/skills/systematic-debugging into .gemini/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install taracodlabs/aiden systematic-debuggingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add taracodlabs/aiden --skill systematic-debugging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/taracodlabs/aiden.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/systematic-debugging .github/skills/systematic-debugging && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "systematic-debugging" agent skill from https://github.com/taracodlabs/aiden/tree/main/skills/systematic-debugging into .github/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add taracodlabs/aiden --skill systematic-debugging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install taracodlabs/aiden systematic-debugging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/taracodlabs/aiden.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/systematic-debugging .opencode/skills/systematic-debugging && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "systematic-debugging" agent skill from https://github.com/taracodlabs/aiden/tree/main/skills/systematic-debugging into .opencode/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
systematic-debugging- GitHub stars
- 849
- Token cost
- ~1.2k tokens
- SKILL.md length
- 305 words
- Files
- 2
- Skills in repo
- 63
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Four-phase root cause investigation for bugs and unexpected behavior
- Works in 4 steps: Reproduce reliably → Isolate the failure → Generate hypotheses → …
- Tasks that involve Debugging
- SKILL.md covers When to Use, How to Use, Examples and Cautions
- Calls git
What it does
Systematic Debugging is an agent skill from taracodlabs/aiden. Four-phase root cause investigation for bugs and unexpected behavior
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.json`).
It sits in Development, covering Debugging and Root cause analysis. The repository describes itself as: Aiden — an autonomous AI agent and work engine built solo. It can operate your browser, terminal, files, apps, APIs, skills and tools, remember context, recover from failures… The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Debugging
- Tasks that involve Root cause analysis
Example prompts
- “/systematic-debugging”
Requirements
- Python 3
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 3704204. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Systematic Debugging loads about 1.2k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 305 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from taracodlabs/aiden at commit 3704204, republished under its Apache-2.0 licence (© taracodlabs). 305 words, ~1,190 tokens.
Download SKILL.mdSave it as
.claude/skills/systematic-debugging/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- systematic-debugging
- description
- Four-phase root cause investigation for bugs and unexpected behavior
- category
- developer
- version
- 1.0.0
- origin
- aiden
- license
- Apache-2.0
- tags
- debugging, root-cause, investigation, bug, error, diagnosis, troubleshooting, logs, testing
Systematic Debugging
A structured four-phase process for diagnosing software bugs: Reproduce → Isolate → Hypothesize → Verify. Prevents guessing and ensures you find the root cause, not just a workaround.
When to Use
- User reports a bug or unexpected behavior without an obvious cause
- An error message appears but the source is unclear
- A fix was applied but the problem persists
- Tests are failing intermittently (flaky tests)
- Production behavior differs from local behavior
How to Use
Phase 1: Reproduce reliably
A bug you can reproduce consistently is halfway solved.
1. Get the exact error message, stack trace, and environment
2. Identify exact steps to trigger the bug
3. Confirm the bug happens in a clean environment (not just local state)
4. Record: OS, runtime version, dependencies, config values
5. Try: does it fail on every run, or only sometimes?If intermittent: add timing, logging, or retry logic to isolate the trigger.
Phase 2: Isolate the failure
Narrow the failure to the smallest possible unit.
1. Add logging before/after suspected areas to find where state diverges
2. Binary search through code: comment out half, does it still fail?
3. Check: when did this last work? (git log, git bisect)
4. Check: what changed recently? (git diff main, dependency updates)
5. Reproduce in a minimal test case — strip away all unrelated code# git bisect to find the breaking commit
git bisect start
git bisect bad # current commit is broken
git bisect good v2.0.0 # last known good tag
# git will checkout commits — test each, then:
git bisect good # or
git bisect bad
# Repeat until git identifies the culprit commit
git bisect resetPhase 3: Generate hypotheses
Form 2-3 specific, testable hypotheses about the root cause.
Bad hypothesis: "Something is wrong with the database"
Good hypothesis: "The connection pool is exhausted under concurrent load
because maxConnections defaults to 5 in test config"
For each hypothesis:
- What evidence supports it?
- What evidence would refute it?
- What one-line change would test it?Rank by probability and test from most to least likely.
Phase 4: Verify and fix
Prove the fix, not just that the error goes away.
1. Apply the smallest change that addresses the root cause
2. Run the original reproduction steps — confirm bug is gone
3. Run the full test suite — confirm no regressions
4. Check edge cases: empty input, null values, concurrent access
5. Write a regression test that would have caught this bug# Regression test template
def test_issue_42_connection_pool_exhaustion():
"""
Regression test: ensure concurrent requests don't exhaust the connection pool.
Root cause: maxConnections was not configurable; defaulted to 5 in test.
Fixed in commit abc123.
"""
results = run_concurrent_requests(count=20)
assert all(r.status_code == 200 for r in results), "Some requests failed under concurrency"Debugging cheat sheet
Error: KeyError / undefined → check input shapes; add null guard
Error: Off-by-one → examine loop bounds and index math
Error: Works locally, fails in CI → check env vars, file paths, timing
Error: Works first run, fails after → check state mutation, cache, side effects
Error: Inconsistent / race condition → check shared mutable state, locks
Error: Memory leak → profile allocations; check event listener cleanupExamples
"My API returns 500 randomly but I can't reproduce it" → Start at Phase 1 — add structured logging with request IDs. Once patterns emerge, apply Phase 2 binary search.
"Tests pass locally but fail in GitHub Actions" → Phase 2: diff the environments (OS, Node version, env vars). Often caused by missing env vars or OS path differences.
"I fixed the bug but it came back after a week" → Phase 4: add a regression test and check if the root cause fix addressed the underlying issue or just a symptom.
Cautions
- Never apply multiple changes at once when debugging — you won't know which one fixed it
- "Works on my machine" is a Phase 1 failure — always reproduce in the target environment
- Logs and print statements are powerful — do not underestimate them in favor of complex tooling
- Document the root cause in the fix commit message so future developers understand why the change was made
© taracodlabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/systematic-debugging of taracodlabs/aiden.
- SKILL.md
- skill.json
Open the folder on GitHubat commit 3704204
Compare with similar skills
Systematic Debugging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Systematic Debugging this skilltaracodlabs/aiden | 849 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| OpenLogi macOS Permissions TriageAprilNEA/OpenLogi | 23k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Bug Finder for daisyUIsaadeghi/daisyui | 43k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Root Cause Debugginggarrytan/gstack | 136k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Graph-Based Bug Tracingtirth8205/code-review-graph | 32k | 1 repos | ~287 | Automated safety check: Pass | MIT | |
| Systematic DebuggingChrisWiles/claude-code-showcase | 6.1k | 3 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
Bug Finder for daisyUI
saadeghi/daisyui
Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.
Root Cause Debugging
garrytan/gstack
Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.
Graph-Based Bug Tracing
tirth8205/code-review-graph
Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.
Systematic Debugging
ChrisWiles/claude-code-showcase
Applies a four-phase debugging routine that finds the root cause of a bug or failing test before any fix is written.
Debugging and Error Recovery
addyosmani/agent-skills
Applies a stop-the-line rule and a step-by-step triage when tests fail, builds break or something stops working, aiming at the root cause instead of guesses.
More from taracodlabs/aiden
All 63 skills in this repoGoogle Flights Search
taracodlabs/aiden
Searches Google Flights for prices, schedules and availability through browser automation with URL-based queries, and stops short of booking.
OpenAI Codex CLI Bridge
taracodlabs/aiden
Delegates code generation, editing and explanation tasks to the OpenAI Codex CLI, with commands for interactive, auto-edit, question-only and model-specific runs.
Google Hotels Search
taracodlabs/aiden
Searches Google Hotels through the agent-browser tool for prices, ratings, amenities and availability, building a search URL from the location and dates and reporting a results table.
HTML Architecture Diagram Maker
taracodlabs/aiden
Generates dark-themed architecture, component, data-flow and network diagrams as self-contained HTML and SVG files that open in any browser.
Indian Broker Portfolio Bridge
taracodlabs/aiden
Aggregates holdings across Zerodha, Upstox and Angel One and normalizes order parameters into one format, with confirmation required before any routing.
arXiv Paper Search
taracodlabs/aiden
Searches arXiv by keyword, category, author or paper ID through its public API and downloads PDFs, with no API key needed.
Related
Categories
Questions about Systematic Debugging
What does Systematic Debugging do?
Four-phase root cause investigation for bugs and unexpected behavior. Systematic Debugging is an agent skill from taracodlabs/aiden.
When should I use Systematic Debugging?
Systematic Debugging fits situations like: tasks that involve Debugging; tasks that involve Root cause analysis.
How do I install Systematic Debugging in Claude Code?
Run `npx skills add taracodlabs/aiden --skill systematic-debugging -a claude-code`. Or copy the skill folder (skills/systematic-debugging in taracodlabs/aiden) into .claude/skills/systematic-debugging in your project. Claude Code loads it when a task matches its description.
How do I install Systematic Debugging in Codex?
Run `npx skills add taracodlabs/aiden --skill systematic-debugging -a codex`. Or copy the skill folder (skills/systematic-debugging in taracodlabs/aiden) into .agents/skills/systematic-debugging in your project. Codex loads it when a task matches its description.
Can I use Systematic Debugging in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add taracodlabs/aiden --skill systematic-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/systematic-debugging, .gemini/skills/systematic-debugging, .github/skills/systematic-debugging and .opencode/skills/systematic-debugging in your project.
What does Systematic Debugging need to run?
Going by SKILL.md and its folder, Systematic Debugging needs the command-line tools its instructions call (git). Our summary lists: Python 3.
Does Systematic Debugging access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Systematic Debugging safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Systematic Debugging use?
Systematic Debugging is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Systematic Debugging use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Systematic Debugging?
Skills that share tags, products or a category with Systematic Debugging: OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars), Root Cause Debugging (garrytan/gstack, 136k stars) and Graph-Based Bug Tracing (tirth8205/code-review-graph, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Systematic Debugging?
taracodlabs (a GitHub organization) maintains it in taracodlabs/aiden, which has 849 GitHub stars. The repository holds 63 skills in this directory. The repository was last updated on September 13, 2026.
Source: taracodlabs/aiden on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.