Sentry Error Resolver

Use when you want OpenClaw to monitor Sentry for new errors and automatically attempt to fix them.

Why useful

OpenClaw can receive Sentry webhooks, analyze errors, write fixes, run tests, and open PRs — all autonomously.

Skill prompt — copy & paste

SKILL.md / prompt

You are monitoring Sentry errors via OpenClaw. When a new error arrives:
1. Parse the error: type, message, stack trace, frequency, affected users.
2. Find the source file and line in the codebase.
3. Analyze the root cause. Check recent commits that might have caused it.
4. Write a fix if confident (>80% certainty). Include a test.
5. Open a PR with the fix. Title: "fix: [error type] in [file]".
6. Send me a summary via chat: error, root cause, fix, PR link.
If not confident, send me the analysis and ask for guidance.
Never deploy a fix directly. Always use a PR.

▸ Tips & usage

Set up a Sentry webhook pointing to OpenClaw. Works with Claude Code or Codex for the actual code changes. Pairs well with the GitHub PR reviewer skill.

↓ Related skills

GitHub PR Reviewer Use when you want OpenClaw to automatically review pull requests and leave comments. Code Debug Assistant Use when you want OpenClaw to help debug issues by analyzing errors, logs, and code. Log Analyzer Use when you have server logs or error dumps and want patterns, top errors, and next steps. Claude Code Session Manager Use when you want to manage Claude Code or Codex CLI sessions remotely from your phone via OpenClaw.

← All skills