New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Spectre Fix

by joenandez in joenandez/spectre

Investigate a reported bug, pin its root cause, and prepare an Execute handoff.

MITAuto-check passedDevelopment

Install Spectre Fix

skills CLI
$ npx skills add joenandez/spectre --skill spectre-fix -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install joenandez/spectre spectre-fix --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/joenandez/spectre.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/spectre/skills/spectre-fix .claude/skills/spectre-fix && rm -rf skills-src

Use ~/.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/

Facts

Skill name
spectre-fix
GitHub stars
164
Token cost
~925 tokens
SKILL.md length
456 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
MIT

At a glance

Investigate a reported bug, pin its root cause, and prepare an Execute handoff.

  • Works in 4 steps: Run Skill(spectre-fix-core) with the bug… → Present the experience contract first in… → In the same response, present one… → …
  • Failing behavior
  • SKILL.md covers Inputs, Working Set, Outputs + DONE and Method / guardrails, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Spectre Fix is an agent skill from joenandez/spectre. Investigate a reported bug, pin its root cause, and prepare an Execute handoff. Use for errors, stack traces, failing behavior, or repro steps. Do NOT use for greenfield work (plan/execute) or a complete repair report (execute).

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging and Root cause analysis. The repository describes itself as: Spectre is a battle-tested 6 stage agentic engineering workflow for building complex, production-ready features. You stay in the loop for the decisions that matter. Your agents…. The licence is MIT.

When your agent uses it

  • Failing behavior
  • Greenfield work (plan/execute)
  • A complete repair report (execute)

Example prompts

  • “/spectre-fix”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Run Skill(spectre-fix-core) with the bug report, PHASE=diagnose, and --orchestrated; require DIAGNOSIS_READY and reject symptom-only…
  2. Present the experience contract first in product language: what users do and observe now, what they will do and observe after repair, and…
  3. In the same response, present one copy-ready host-specific spectre-execute {BUG_REPORT_PATH} --origin fix. Never repair from Fix; invoking…
  4. Feedback revises the report and refreshes the command; it does not enter an approval loop.

What it can do on your machine

Read from SKILL.md and the folder at commit 931c9e8. 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

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

Spectre Fix loads about 925 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 456 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~925

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 joenandez/spectre at commit 931c9e8, republished under its MIT licence (© joenandez). 456 words, ~925 tokens.

Download SKILL.mdSave it as .claude/skills/spectre-fix/SKILL.md (or your agent's skills folder).
name
spectre-fix
description
Investigate a reported bug, pin its root cause, and prepare an Execute handoff. Use for errors, stack traces, failing behavior, or repro steps. Do NOT use for greenfield work (plan/execute) or a complete repair report (execute).
user-invocable
true
disable-model-invocation
true

fix

Standalone diagnosis-to-Execute bug workflow. Delegate diagnosis to spectre-fix-core; never implement.

Inputs

  • bug_report ($ARGUMENTS): error/stack trace, repro steps, context. If empty, ask the user for error message, repro steps, and relevant context before proceeding.

Working Set

  • Resolve one managed BUG_ROOT: an explicitly named managed root wins; otherwise load and follow @skill-spectre:spectre-feature-root with KIND=bug through DONE. Never adopt an ambient feature root. Keep writes beneath it and pass it unchanged.
  • The bug report plus the exact in-thread diagnosis and experience contract returned by spectre-fix-core.
  • Affected paths, history, analysts, tests, and diagnostics are owned by the core and read just-in-time.

Outputs + DONE

The core's full diagnosis and experience contract rendered in-thread, mirrored in full into a self-locating managed repair plan at {BUG_REPORT_PATH} before code mutation, recording Bug, Bug Root, and the reported problem in the user's own words, plus an explicit Execute handoff. DONE when:

  • Root cause and candidate repair boundary are grounded, not symptom-suppressed — name the cause and affected files.
  • The transcript carries every contract row with its evidence; the plan beneath the managed bug root matches it. A file path is not a presentation.
  • The current→expected experience, preserved invariants, and disclosed collateral changes are explicit; every row is resolved.
  • The same response gives the exact bug-report path, explicit fix origin, and one copy-ready Execute invocation that works in a fresh session.
  • Command display is non-mutating; invoking Execute is the mutation boundary.
Show full SKILL.md (225 more words)Show less

Method / guardrails

  1. Run Skill(spectre-fix-core) with the bug report, PHASE=diagnose, and --orchestrated; require DIAGNOSIS_READY and reject symptom-only explanations.
  2. Present the experience contract first in product language: what users do and observe now, what they will do and observe after repair, and which adjacent journeys change or remain unchanged. Then present the root cause, affected files, repair boundary, and verification plan; resolve every unresolved row. Mirror that render into {BUG_ROOT}/bug-report.md, using a scoped name if one already exists; capture the exact written path as BUG_REPORT_PATH; never alter canonical Scope or overwrite a reviewed plan.
  3. In the same response, present one copy-ready host-specific spectre-execute {BUG_REPORT_PATH} --origin fix. Never repair from Fix; invoking Execute is the mutation boundary.
  4. Feedback revises the report and refreshes the command; it does not enter an approval loop.

Handoff

HandoffDetails
🧭 Current phaseDone
📦 What was just doneResult
▶️ Proposed next stepRender resolved action.

Return diagnosis/contract + one Execute route; closeout commits report, never repair. Render Execute with resolved absolute bug-report path + --origin fix.

Escalate-If

  • Bug report is empty or too thin to form hypotheses → ask the user for error, repro, and context.
  • Investigation contradicts every hypothesis (no root cause found) → report findings and ask for more repro detail rather than guessing a fix.
  • Desired behavior is unclear, an unresolved row remains, or a collateral change exceeds the reported repair.

© joenandez, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/spectre/skills/spectre-fix of joenandez/spectre.

Open the folder on GitHubat commit 931c9e8

Compare with similar skills

Spectre Fix 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.

Spectre Fix compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Spectre Fix this skilljoenandez/spectre164—~925Automated safety check: PassMIT
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
Bug Finder for daisyUIsaadeghi/daisyui43k—~2.3kAutomated safety check: PassMIT
Root Cause Debugginggarrytan/gstack136k—~1.4kAutomated safety check: PassMIT
Graph-Based Bug Tracingtirth8205/code-review-graph32k1 repos~287Automated safety check: PassMIT
Systematic DebuggingChrisWiles/claude-code-showcase6.1k3 repos~1.2kAutomated safety check: PassNone

Similar skills

  • 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.

    23k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: notes

  • 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.

    43k GitHub stars~2.3k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • 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.

    136k GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • 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.

    32k GitHub starsUsed in 1 repo~287 tokens
    DevelopmentAuto-check passed

  • 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.

    6.1k GitHub starsUsed in 3 repos~1.2k tokens
    DevelopmentAuto-check passed

  • 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.

    104k GitHub starsUsed in 1 repo~2.6k tokens
    DevelopmentAuto-check passed

More from joenandez/spectre

All 26 skills in this repo

  • Verify Spectre

    joenandez/spectre

    A skill your agent uses when validating that the Spectre plugin itself still works after ANY change to this repo — skills, prompts, agents, hooks, the CLI, the Codex mirror, or a release.

    164 GitHub stars~1.5k tokensUpdated 8 days ago
    Auto-check passed

  • Feature Codex Spectre Implementation

    joenandez/spectre

    A skill your agent uses when modifying the Codex SPECTRE install flow, SessionStart continuity, project skill syncing, registry injection, or Codex-specific runtime files.

    164 GitHub stars~2.2k tokensUpdated 8 days ago
    Auto-check passed

  • Spectre Handoff

    joenandez/spectre

    Save a quiet, branch-keyed session snapshot with continuity, active work, and optional task/todo state for automatic resume.

    164 GitHub stars~1.3k tokensUpdated 8 days ago
    Auto-check passed

  • Spectre Learn

    joenandez/spectre

    User-invoked front door for durable capture. An agent skill from joenandez/spectre.

    164 GitHub stars~1k tokensUpdated 8 days ago
    Auto-check passed

  • Spectre Rewrite Skill

    joenandez/spectre

    Rewrite a verbose SPECTRE skill into a compact, contract-form Spectre skill proposal — clear on WHAT, silent on HOW — grounded in the spectre-light distillation and freedom-tier budget.

    164 GitHub stars~3k tokensUpdated 8 days ago
    Auto-check passed

  • Spectre Rewrite Subagent

    joenandez/spectre

    Rewrite Spectre subagent definitions into compact, contract-driven agents with clear routing, least-privilege tools, output schemas, and an auditable rewrite trail.

    164 GitHub stars~1.8k tokensUpdated 8 days ago
    Auto-check passed

Categories

Questions about Spectre Fix

What does Spectre Fix do?

Investigate a reported bug, pin its root cause, and prepare an Execute handoff. Spectre Fix is an agent skill from joenandez/spectre. Investigate a reported bug, pin its root cause, and prepare an Execute handoff.

When should I use Spectre Fix?

Spectre Fix fits situations like: failing behavior; greenfield work (plan/execute); A complete repair report (execute).

How do I install Spectre Fix in Claude Code?

Run `npx skills add joenandez/spectre --skill spectre-fix -a claude-code`. Or copy the skill folder (plugins/spectre/skills/spectre-fix in joenandez/spectre) into .claude/skills/spectre-fix in your project. Claude Code loads it when a task matches its description.

How do I install Spectre Fix in Codex?

Run `npx skills add joenandez/spectre --skill spectre-fix -a codex`. Or copy the skill folder (plugins/spectre/skills/spectre-fix in joenandez/spectre) into .agents/skills/spectre-fix in your project. Codex loads it when a task matches its description.

Can I use Spectre Fix 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 joenandez/spectre --skill spectre-fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spectre-fix, .gemini/skills/spectre-fix, .github/skills/spectre-fix and .opencode/skills/spectre-fix in your project.

What does Spectre Fix need to run?

SKILL.md names no scripts, command-line tools or credentials: Spectre Fix is instructions for the agent only.

Does Spectre Fix access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Spectre Fix 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 Spectre Fix use?

Spectre Fix is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Spectre Fix use?

About 925 tokens (SKILL.md is roughly 3.7k 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 Spectre Fix?

Skills that share tags, products or a category with Spectre Fix: 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 Spectre Fix?

joenandez (a GitHub user) maintains it in joenandez/spectre, which has 164 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 2, 2026.

Source: joenandez/spectre on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.