sentry-cli

What This Skill Does

The sentry-cli skill provides a command-line interface for the OpenClaw agent to interact directly with Sentry.io. This integration enables the automation of error tracking workflows, release management, and critical debug artifact uploads. By utilizing this skill, your agent can bridge the gap between your CI/CD pipelines and your monitoring dashboard, ensuring that every deployment is correctly tagged, source maps are de-obfuscated, and native debug symbols are available for crash reporting. It transforms Sentry from a passive dashboard into an active participant in your development lifecycle.

Installation

To integrate this skill into your environment, use the OpenClaw command: clawhub install openclaw/skills/skills/iahmadzain/sentry-cli. Ensure that your environment has the sentry-cli binary installed via Homebrew, npm, or direct download. After installation, authenticate your agent by running sentry-cli login or by exporting the SENTRY_AUTH_TOKEN environment variable. For team environments, it is recommended to create a .sentryclirc file in the root directory to store your organization and project defaults.

Use Cases

This skill is indispensable for DevOps engineers and developers. Use it to automate the release workflow by creating and finalizing releases during deployment. It is particularly powerful for front-end developers who need to automatically upload source maps to make minified code readable in Sentry. Additionally, mobile developers can use it to upload dSYMs for iOS and ProGuard mappings for Android. The skill also facilitates issue management, allowing your agent to query, resolve, or mute issues directly from the chat interface. Finally, it serves as a monitor for cron jobs, allowing the agent to track job status and send health check-ins.

Example Prompts

1. "Check the current status of the production release and list any unresolved high-priority issues."
2. "Finalize the release for version 2.4.1 and upload all source maps located in the ./dist directory."
3. "Resolve issue SENTRY-123 and mark it as fixed in the next deployment cycle."

Tips & Limitations

Always use absolute paths when uploading artifacts to ensure consistency across different agent execution environments. When managing releases in CI/CD, prefer the --finalize flag to reduce network round-trips. Note that debug file uploads can be heavy on network bandwidth; ensure your environment has a stable connection for large dSYM uploads. Be cautious when using the issues resolve command as it may hide genuine regressions; ensure your agent has context on whether the fix has been verified.