Agent skill · Testing & QA

trace

Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why is this failing", "this test is broken".

jeremylongshoregithub.com/jeremylongshoreGitHub ↗
claude-coderead-onlyMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill trace --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 20 KB
Bundled scripts: none
Version: 3.1.3
Allowed tools: ReadBash(git:*)Bash(npm:*)Bash(pnpm:*)GlobGrepAgentAskUserQuestion
Requires: Designed for Claude Code
Path: plugins/ai-agency/hyperflow/skills/trace/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,596
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Trace Root cause, not symptom. Never patch over a bug without understanding why it happened. All agents inherit the session model. Reviewers and Debuggers bold-labeled; Workers plain. ## Per-Step Agent Map (DOCTRINE rule 12) Every substantive step dispatches at least one Agent. Atomic steps (per DOCTRINE 12.2.8) are a single Worker → Reviewer pair with no independent angles to fan out. | Step |

More from claude-code-plugins-plus-skills
All skills →
building-automl-pipelinesBuild automated machine learning pipelines with feature engineering, model selection, and…Data & Analyticsprocessing-computer-vision-tasksProcess images using object detection, classification, and segmentation. Use when requesting…AI & Agentsvalidating-ai-ethics-and-fairnessValidate AI/ML models and datasets for bias, fairness, and ethical concerns. Use when auditing AI…AI & Agentsorchestrating-multi-agent-systemsExecute orchestrate multi-agent systems with handoffs, routing, and workflows across AI providers.…Workflow & Productivityrunning-clustering-algorithmsAnalyze datasets by running clustering algorithms (K-means, DBSCAN, hierarchical) to identify data…Data & Analyticspreprocessing-data-with-automated-pipelinesProcess automate data cleaning, transformation, and validation for ML tasks. Use when requesting…Data & Analytics
About this skill
What does the trace skill do?

Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why is this failing", "this test is broken".

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill trace --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.