rollbar_skill
- Go
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill robzolkos/rollbar-cli --skill rollbar- SKILL.md4.3 KB
Overview
This skill integrates Rollbar error tracking into an agent or CLI workflow to inspect, investigate, and resolve production errors. It helps you list recent issues, fetch full context for bug fixes, and mark items resolved after deploying fixes. Use it to quickly triage overnight errors, deep-dive into stack traces, and automate common Rollbar queries.
How this skill works
The skill issues Rollbar CLI commands using the configured access token or .rollbar.yaml config to query items, occurrences, and detailed context. It supports filters like time range, level, environment, and status, and returns results in table, json, compact/ai, or markdown formats. For resolution actions it uses a write-scoped token to mark items resolved by ID or UUID.
When to use it
- You want a quick list of errors from the last X hours or overnight.
- You need full context (stack trace, request data, user info) to fix a bug reported by Rollbar.
- You must find frequent or specific errors by query, level, or environment.
- You want to view recent occurrences or details for a single occurrence.
- You need to mark one or more Rollbar items as resolved after a fix is deployed.
Best practices
- Set ROLLBAR_ACCESS_TOKEN or include a .rollbar.yaml in the project for authentication.
- Use --since with human-friendly times (e.g., "8 hours ago", "24h") to scope searches.
- Prefer --env production and --level error,critical for noisy production triage.
- Use --output compact or --output ai when feeding results into an LLM to save tokens.
- Ensure the token has write scope before attempting resolve operations to avoid permission errors.
Example use cases
- Triage overnight production errors: rollbar items --since "12 hours ago" --level error,critical --env production --ai
- Investigate a specific issue: rollbar context 123 (or rollbar context 123 --occurrences 5 for multiple samples)
- Find the most frequent errors: rollbar items --sort occurrences --limit 10
- Inspect a single occurrence with request and user details: rollbar occurrence 453568801204
- Resolve fixed issues: rollbar resolve 93 95 (requires write-scoped token)
FAQ
Set ROLLBAR_ACCESS_TOKEN in the environment or place a .rollbar.yaml config in the project. Resolving items requires a token with write scope.
Which output should I use for automated analysis?
Use --output json for full machine parsing. Use --output compact or --output ai when sending data to an LLM to reduce token usage.