agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/elements/.agents/skills/troubleshooting/SKILL.md

troubleshooting

Skill115 starsChanged 55 days agoApache-2.0View on GitHub

Diagnose and resolve common issues including test failures, build errors, performance regressions, and development environment problems. Use this skill whenever the user reports something broken, failing, timing out, hanging, or producing unexpected results. Trigger on test failures (elementIsStable timeouts, flaky tests, screenshot diffs), build errors (Cannot find module, wireit cache issues, stale output), CI/CD failures, Git LFS problems, port conflicts, lighthouse score regressions, SSR errors, or environment setup issues.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use task-breakdown and architecture.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ttmouseSkill

    task-breakdown

    专业的任务拆解器，将复杂需求拆分成"独立可运行与可演示"的最小闭环任务卡。严格按照纵向切片、单一数据变化、单一入口原则，确保每张任务卡都能在单回合实现并验证。当用户说"帮我拆解一下任务"、"用任务拆解器分析"、"按规范拆分"或需要将一个大的开发需求拆分成可执行的小任务时使用。输出格式严格按照[src/renderer/TODO.md]标准存储。

    Also in 3 projects that use this

  • AnthropicSkill

    architecture

    Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the troubleshooting guide to get critical context for troubleshooting guidance.

    line 23
  2. Very specific:

    Test failures: pnpm run test -- src/<component>/<component>.test.ts (isolate the failing test)

    line 36

“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Troubleshooting

You MUST review the troubleshooting guideline when diagnosing test failures, build errors, or performance issues.

When to Use This Skill

  • Debugging unit test failures or timing issues
  • Investigating visual regression test differences
  • Troubleshooting Lighthouse performance scores
  • Resolving build failures or Wireit cache issues
  • Fixing Git LFS problems with visual baselines
  • Diagnosing CI/CD pipeline failures
  • Resolving development environment setup issues
  • Investigating performance regressions in tests or builds

Must Read File

Read the troubleshooting guide to get critical context for troubleshooting guidance.

Diagnostic Triage Workflow

  1. Identify the symptom category:

    • Test failure:unit, axe, visual, SSR, or lighthouse?
    • Build failure:Wireit cache, dependency resolution, TypeScript, or circular imports?
    • Environment issue:Node version, pnpm version, Git LFS, or port conflict?
    • Performance regression:slow tests, slow builds, or large bundles?

  2. Run the relevant diagnostic commands:

    • Test failures: pnpm run test -- src/<component>/<component>.test.ts (isolate the failing test)
    • Build failures: pnpm run ci:reset then pnpm run build (clear caches first)
    • Environment: node --version && pnpm --version && git lfs env (verify toolchain)
  3. Check the matching section in the troubleshooting guide for the specific symptom/solution pair.
  4. If the issue persists, compare against a working reference component (badge, button, or card) to spot structural differences.

References

  • Troubleshooting Guide - Common issues and solutions
  • Testing Guidelines - Test patterns
  • Unit Testing - Unit test details
  • Visual Testing - Visual regression details
  • Lighthouse Testing - Performance testing
  • Build System - Wireit troubleshooting

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free