E2E
callstack/react-native-pager-view
Agentic end-to-end tests with e2e, the e2e runner. An agent skill from callstack/react-native-pager-view.
Disciplined diagnosis loop for hard bugs and performance regressions.
Install Diagnose
$ npx skills add ywwynm/EverythingDone --skill diagnose -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ywwynm/EverythingDone diagnose --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/ywwynm/EverythingDone.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/diagnose .claude/skills/diagnose && 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 "diagnose" agent skill from https://github.com/ywwynm/EverythingDone/tree/master/.agents/skills/diagnose into .claude/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", 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/ywwynm/EverythingDone/tree/master/.agents/skills/diagnoseType 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 ywwynm/EverythingDone --skill diagnose -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ywwynm/EverythingDone diagnose --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ywwynm/EverythingDone.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/diagnose .agents/skills/diagnose && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "diagnose" agent skill from https://github.com/ywwynm/EverythingDone/tree/master/.agents/skills/diagnose into .agents/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", 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 ywwynm/EverythingDone --skill diagnose -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ywwynm/EverythingDone diagnose --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ywwynm/EverythingDone.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/diagnose .cursor/skills/diagnose && 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 "diagnose" agent skill from https://github.com/ywwynm/EverythingDone/tree/master/.agents/skills/diagnose into .cursor/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", 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/ywwynm/EverythingDone.git --path .agents/skills/diagnose--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 ywwynm/EverythingDone --skill diagnose -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ywwynm/EverythingDone diagnose --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ywwynm/EverythingDone.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/diagnose .gemini/skills/diagnose && 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 "diagnose" agent skill from https://github.com/ywwynm/EverythingDone/tree/master/.agents/skills/diagnose into .gemini/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", 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 ywwynm/EverythingDone diagnoseInstalls 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 ywwynm/EverythingDone --skill diagnose -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ywwynm/EverythingDone.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/diagnose .github/skills/diagnose && 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 "diagnose" agent skill from https://github.com/ywwynm/EverythingDone/tree/master/.agents/skills/diagnose into .github/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", 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 ywwynm/EverythingDone --skill diagnose -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ywwynm/EverythingDone diagnose --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ywwynm/EverythingDone.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/diagnose .opencode/skills/diagnose && 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 "diagnose" agent skill from https://github.com/ywwynm/EverythingDone/tree/master/.agents/skills/diagnose into .opencode/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", 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
diagnose- GitHub stars
- 144
- Used in
- 17 other repos
- Token cost
- ~1.8k tokens
- SKILL.md length
- 1,059 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Disciplined diagnosis loop for hard bugs and performance regressions.
- Works in 6 steps: Build a feedback loop → Reproduce → Hypothesise → …
- User says diagnose this / debug this
- SKILL.md covers Phase 1 — Build a feedback loop, Phase 2 — Reproduce, Phase 3 — Hypothesise and Phase 4 — Instrument, plus 2 more sections
- Runs Shell scripts from its folder; calls git
What it does
Diagnose is an agent skill from ywwynm/EverythingDone. Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/hitl-loop.template.sh`).
It sits in Testing & QA. It works with Android. The repository describes itself as: EverythingDone, an Android app to help you remember things, and finish them! The licence is GPL-3.0.
When your agent uses it
- User says diagnose this / debug this
- Says something is broken/throwing/failing
- Describes a performance regression
Example prompts
- “diagnose this”
- “debug this”
- “/diagnose”
Requirements
- A Bash shell
Workflow steps
6 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 bc5f3f7. 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
Ships 1 file in scripts/ (Shell), which the agent can run.
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
Diagnose loads about 1.8k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 1,059 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); the scripts in this folder are not scanned.
SKILL.md
The full file from ywwynm/EverythingDone at commit bc5f3f7, republished under its GPL-3.0 licence (© ywwynm). 1,059 words, ~1,779 tokens.
Download SKILL.mdSave it as
.claude/skills/diagnose/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- diagnose
- description
- Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Diagnose
A discipline for hard bugs. Skip phases only when explicitly justified.
When exploring the codebase, use the project's domain glossary to get a clear mental model of the relevant modules, and check ADRs in the area you're touching.
Phase 1 — Build a feedback loop
This is the skill. Everything else is mechanical. If you have a fast, deterministic, agent-runnable pass/fail signal for the bug, you will find the cause — bisection, hypothesis-testing, and instrumentation all just consume that signal. If you don't have one, no amount of staring at code will save you.
Spend disproportionate effort here. Be aggressive. Be creative. Refuse to give up.
Ways to construct one — try them in roughly this order
- Failing test at whatever seam reaches the bug — unit, integration, e2e.
- Curl / HTTP script against a running dev server.
- CLI invocation with a fixture input, diffing stdout against a known-good snapshot.
- Headless browser script (Playwright / Puppeteer) — drives the UI, asserts on DOM/console/network.
- Replay a captured trace. Save a real network request / payload / event log to disk; replay it through the code path in isolation.
- Throwaway harness. Spin up a minimal subset of the system (one service, mocked deps) that exercises the bug code path with a single function call.
- Property / fuzz loop. If the bug is "sometimes wrong output", run 1000 random inputs and look for the failure mode.
- Bisection harness. If the bug appeared between two known states (commit, dataset, version), automate "boot at state X, check, repeat" so you can
git bisect runit. - Differential loop. Run the same input through old-version vs new-version (or two configs) and diff outputs.
- HITL bash script. Last resort. If a human must click, drive them with
scripts/hitl-loop.template.shso the loop is still structured. Captured output feeds back to you.
Build the right feedback loop, and the bug is 90% fixed.
Iterate on the loop itself
Treat the loop as a product. Once you have a loop, ask:
- Can I make it faster? (Cache setup, skip unrelated init, narrow the test scope.)
- Can I make the signal sharper? (Assert on the specific symptom, not "didn't crash".)
- Can I make it more deterministic? (Pin time, seed RNG, isolate filesystem, freeze network.)
A 30-second flaky loop is barely better than no loop. A 2-second deterministic loop is a debugging superpower.
Non-deterministic bugs
The goal is not a clean repro but a higher reproduction rate. Loop the trigger 100×, parallelise, add stress, narrow timing windows, inject sleeps. A 50%-flake bug is debuggable; 1% is not — keep raising the rate until it's debuggable.
When you genuinely cannot build a loop
Stop and say so explicitly. List what you tried. Ask the user for: (a) access to whatever environment reproduces it, (b) a captured artifact (HAR file, log dump, core dump, screen recording with timestamps), or (c) permission to add temporary production instrumentation. Do not proceed to hypothesise without a loop.
Do not proceed to Phase 2 until you have a loop you believe in.
Phase 2 — Reproduce
Run the loop. Watch the bug appear.
Confirm:
- The loop produces the failure mode the user described — not a different failure that happens to be nearby. Wrong bug = wrong fix.
- The failure is reproducible across multiple runs (or, for non-deterministic bugs, reproducible at a high enough rate to debug against).
- You have captured the exact symptom (error message, wrong output, slow timing) so later phases can verify the fix actually addresses it.
Do not proceed until you reproduce the bug.
Show full SKILL.md (473 more words)Show less
Phase 3 — Hypothesise
Generate 3–5 ranked hypotheses before testing any of them. Single-hypothesis generation anchors on the first plausible idea.
Each hypothesis must be falsifiable: state the prediction it makes.
Format: "If
<X>is the cause, then<changing Y>will make the bug disappear /<changing Z>will make it worse."
If you cannot state the prediction, the hypothesis is a vibe — discard or sharpen it.
Show the ranked list to the user before testing. They often have domain knowledge that re-ranks instantly ("we just deployed a change to #3"), or know hypotheses they've already ruled out. Cheap checkpoint, big time saver. Don't block on it — proceed with your ranking if the user is AFK.
Phase 4 — Instrument
Each probe must map to a specific prediction from Phase 3. Change one variable at a time.
Tool preference:
- Debugger / REPL inspection if the env supports it. One breakpoint beats ten logs.
- Targeted logs at the boundaries that distinguish hypotheses.
- Never "log everything and grep".
Tag every debug log with a unique prefix, e.g. [DEBUG-a4f2]. Cleanup at the end becomes a single grep. Untagged logs survive; tagged logs die.
Perf branch. For performance regressions, logs are usually wrong. Instead: establish a baseline measurement (timing harness, performance.now(), profiler, query plan), then bisect. Measure first, fix second.
Phase 5 — Fix + regression test
Write the regression test before the fix — but only if there is a correct seam for it.
A correct seam is one where the test exercises the real bug pattern as it occurs at the call site. If the only available seam is too shallow (single-caller test when the bug needs multiple callers, unit test that can't replicate the chain that triggered the bug), a regression test there gives false confidence.
If no correct seam exists, that itself is the finding. Note it. The codebase architecture is preventing the bug from being locked down. Flag this for the next phase.
If a correct seam exists:
- Turn the minimised repro into a failing test at that seam.
- Watch it fail.
- Apply the fix.
- Watch it pass.
- Re-run the Phase 1 feedback loop against the original (un-minimised) scenario.
Phase 6 — Cleanup + post-mortem
Required before declaring done:
- Original repro no longer reproduces (re-run the Phase 1 loop)
- Regression test passes (or absence of seam is documented)
- All
[DEBUG-...]instrumentation removed (grepthe prefix) - Throwaway prototypes deleted (or moved to a clearly-marked debug location)
- The hypothesis that turned out correct is stated in the commit / PR message — so the next debugger learns
Then ask: what would have prevented this bug? If the answer involves architectural change (no good test seam, tangled callers, hidden coupling) hand off to the /improve-codebase-architecture skill with the specifics. Make the recommendation after the fix is in, not before — you have more information now than when you started.
© ywwynm, GPL-3.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 (scripts) in .agents/skills/diagnose of ywwynm/EverythingDone.
- SKILL.md
- scripts/hitl-loop.template.sh
Open the folder on GitHubat commit bc5f3f7
Used in 17 other repositories
We found 18 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 17 other GitHub owners. This page covers the copy in ywwynm/EverythingDone, which our catalogue first saw on October 7, 2026.
- DevBetterCom/DevBetterWeb.agents/skills/diagnose
- smontlouis/bible-strong.agents/skills/diagnose
- AvdLee/RocketSimAppdocs/.agents/skills/diagnose
- modernweb-dev/rocket.agents/skills/diagnose
- alex-on-ai/WebReaper.agents/skills/diagnose
- EpicenterHQ/epicenter.agents/skills/diagnose
- victorgarciaesgi/regle.cursor/skills/diagnose
- yamcodes/arkenvskills/diagnose
- InditexTech/weavejs.agents/skills/diagnose
- letehaha/moneymatter.claude/skills/diagnose
- opensage-agent/opensage-adksrc/opensage/bash_tools/diagnose
- stevesolun/ctximported-skills/mattpocock/diagnose
- appleweiping/WEIPING_WIKI.claude/skills/mattpocock-skills/skills/engineering/diagnose
- aurorasoft2/Matt_Pocock_Skillsskills/engineering/diagnose
- openvetta/open-vetta.agents/skills/diagnose
- aiskillstore/marketplaceskills/mattpocock/diagnose
- infometa/workbuddyskillsskills/diagnose
Compare with similar skills
Diagnose 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 |
|---|---|---|---|---|---|---|
| Diagnose this skillywwynm/EverythingDone | 144 | 17 repos | ~1.8k | Automated safety check: Pass | GPL-3.0 | |
| E2Ecallstack/react-native-pager-view | 3.4k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| SoloPi AI Controlalipay/SoloPi | 6.3k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| E2Egronxb/hot-updater | 1.8k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Testing SkillTypeCellOS/BlockNote | 10k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Mesh Labpermissionlesstech/bitchat-android | 7.8k | — | ~2.9k | Automated safety check: Pass | GPL-3.0 |
Similar skills
SoloPi AI Control
alipay/SoloPi
Drives Android devices through SoloPi's typed command line to record, replay and verify app behavior, with device pools and signed on-device decision models.
E2E
gronxb/hot-updater
Run end-to-end OTA verification for examples/v0.85.0 with agent-device.
Testing Skill
TypeCellOS/BlockNote
Instructions for writing, running, and updating unit/end-to-end tests.
Mesh Lab
permissionlesstech/bitchat-android
Run, diagnose, and extend bitchat Android Mesh Lab physical-device tests.
BrowserStack Live Testing
handsontable/handsontable
Opens a live BrowserStack session on a real Android, iOS or desktop browser for a local or public URL, tunneling localhost through Cloudflare when needed.
More from ywwynm/EverythingDone
Triage
ywwynm/EverythingDone
Triage issues through a state machine driven by triage roles.
Improve Codebase Architecture
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
To Issues
ywwynm/EverythingDone
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
To Prd
ywwynm/EverythingDone
Turn the current conversation context into a PRD and publish it to the project issue tracker.
Setup Matt Pocock Skills
ywwynm/EverythingDone
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
Related
Works with
Categories
Questions about Diagnose
What does Diagnose do?
Disciplined diagnosis loop for hard bugs and performance regressions. Diagnose is an agent skill from ywwynm/EverythingDone. Disciplined diagnosis loop for hard bugs and performance regressions.
When should I use Diagnose?
Diagnose fits situations like: user says diagnose this / debug this; says something is broken/throwing/failing; describes a performance regression.
How do I install Diagnose in Claude Code?
Run `npx skills add ywwynm/EverythingDone --skill diagnose -a claude-code`. Or copy the skill folder (.agents/skills/diagnose in ywwynm/EverythingDone) into .claude/skills/diagnose in your project. Claude Code loads it when a task matches its description.
How do I install Diagnose in Codex?
Run `npx skills add ywwynm/EverythingDone --skill diagnose -a codex`. Or copy the skill folder (.agents/skills/diagnose in ywwynm/EverythingDone) into .agents/skills/diagnose in your project. Codex loads it when a task matches its description.
Can I use Diagnose 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 ywwynm/EverythingDone --skill diagnose -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/diagnose, .gemini/skills/diagnose, .github/skills/diagnose and .opencode/skills/diagnose in your project.
What does Diagnose need to run?
Going by SKILL.md and its folder, Diagnose needs a shell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell.
Does Diagnose 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 Diagnose 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Diagnose use?
Diagnose is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Diagnose use?
About 1.8k tokens (SKILL.md is roughly 7.1k 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 Diagnose?
Skills that share tags, products or a category with Diagnose: E2E (callstack/react-native-pager-view, 3.4k stars), SoloPi AI Control (alipay/SoloPi, 6.3k stars), E2E (gronxb/hot-updater, 1.8k stars) and Testing Skill (TypeCellOS/BlockNote, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Diagnose?
ywwynm (a GitHub user) maintains it in ywwynm/EverythingDone, which has 144 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.
Source: ywwynm/EverythingDone on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.