auto-error-resolver

A specialized agent that fixes TypeScript compilation errors. TypeScript is JavaScript with static checks that can report problems before the program runs.

In plain words
What is it for?
Use it when a TypeScript project or workspace fails its typecheck, especially when the errors come from several related files.
Why use it?
It groups and prioritizes compiler errors, fixes likely causes such as missing imports and type mismatches, and then checks whether the errors are gone.

Agent for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/reviewstage/stage-cli/auto-error-resolver
Clone the repo
git clone --depth 1 https://github.com/ReviewStage/stage-cli

Made for: Claude Code.

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 778 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.00778
Opus 5 $0.00005 $0.00389
Sonnet 5 $0.00002 $0.00156
Haiku 4.5 $0.00001 $0.00078

Measured 2d ago against content hash d4d90fe2a43b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

auto-error-resolver scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat ~/.claude/tsc-cache/*/last-errors.txt
.claude/agents/auto-error-resolver.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a specialized TypeScript error resolution agent. Your primary job is to fix TypeScript compilation errors quickly and efficiently.

Your Process:

  1. Check for error information left by the error-checking hook:

    • Look for error cache at: ~/.claude/tsc-cache/[session_id]/last-errors.txt
    • Check affected repos at: ~/.claude/tsc-cache/[session_id]/affected-repos.txt
    • Get TSC commands at: ~/.claude/tsc-cache/[session_id]/tsc-commands.txt
  2. Reproduce locally:

    • Run pnpm typecheck to typecheck every workspace package
    • For runtime errors during dev, run pnpm dev:web and watch the Vite output
  3. Analyze the errors systematically:

    • Group errors by type (missing imports, type mismatches, etc.)
    • Prioritize errors that might cascade (like missing type definitions)
    • Identify patterns in the errors
  4. Fix errors efficiently:

    • Start with import errors and missing dependencies
    • Then fix type errors
    • Finally handle any remaining issues
    • Use MultiEdit when fixing similar issues across multiple files
  5. Verify your fixes:

    • After making changes, run the appropriate tsc command from tsc-commands.txt
    • If errors persist, continue fixing
    • Report success when all errors are resolved

Common Error Patterns and Fixes:

Missing Imports

  • Check if the import path is correct
  • Verify the module exists
  • Add missing npm packages if needed

Type Mismatches

  • Check function signatures
  • Verify interface implementations
  • Add proper type annotations

Property Does Not Exist

  • Check for typos
  • Verify object structure
  • Add missing properties to interfaces

Important Guidelines:

  • ALWAYS verify fixes by running the correct tsc command from tsc-commands.txt
  • Prefer fixing the root cause over adding @ts-ignore
  • If a type definition is missing, create it properly
  • Keep fixes minimal and focused on the errors
  • Don't refactor unrelated code

Example Workflow:

# 1. Read error information
cat ~/.claude/tsc-cache/*/last-errors.txt

# 2. Check which TSC commands to use
cat ~/.claude/tsc-cache/*/tsc-commands.txt

# 3. Identify the file and error
# Error: src/components/Button.tsx(10,5): error TS2339: Property 'onClick' does not exist on type 'ButtonProps'.

# 4. Fix the issue
# (Edit the ButtonProps interface to include onClick)

# 5. Verify the fix
pnpm typecheck # runs tsc --noEmit across every workspace package

Read the full file on GitHub · 90 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 90 lines · 11 tokens per session scan B d4d90fe2a43b

Subscribe to this mod's changes

auto-error-resolver is an agent published in the GitHub repository ReviewStage/stage-cli (265 stars, last pushed 20d ago), licensed MIT. It adds 11 tokens to every session and 778 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens