Skip to content

Replace Sentry API helper with CLI-first skills#195

Open
HazAT wants to merge 5 commits into
openai:mainfrom
HazAT:codex/sentry-cli-skill
Open

Replace Sentry API helper with CLI-first skills#195
HazAT wants to merge 5 commits into
openai:mainfrom
HazAT:codex/sentry-cli-skill

Conversation

@HazAT
Copy link
Copy Markdown
Collaborator

@HazAT HazAT commented Apr 27, 2026

Hey, I am Daniel

I work at Sentry. We updated our Skill here cause we wanna make sure users experience our product always the we intend them to. In the newest agentic way - since stuff changes so quickly, we wanna default to our CLI being used; it's also better in locally detecting our users config for Sentry.
Also added another Skill that uses all of our specialized Skill for setting up Sentry and do instrumentation of our SDKs - proxied through skills.sentry.dev to our github repo here: https://github.com/getsentry/sentry-for-ai

There will probably be more changes coming in the future but we want to keep it like this for now.

(We still need to figure out if we could use CLI locally and MCP in your cloud env, that would be cool)

HazAT added 3 commits April 10, 2026 21:04
Raise the Sentry plugin version to 0.2.0 to reflect the recent CLI-first skill overhaul. This keeps the plugin manifest aligned with the expanded capabilities and ensures the upstream PR includes the intended release metadata update.
@HazAT HazAT requested a review from a team April 27, 2026 18:25
HazAT added 2 commits May 6, 2026 16:45
Update the Sentry plugin manifest so both the package author and displayed developer attribution point to Sentry. This keeps the marketplace metadata aligned with the plugin owner after the CLI-first skill update.
@HazAT
Copy link
Copy Markdown
Collaborator Author

HazAT commented Jun 2, 2026

Sorry for the ping @ashwinm-oai @moustafa-openai but can we get approval here - the plugin you shipped was a good start but not really a good representation and the way we want people to interact with Sentry 😅
So it would be great if we could merge this
We are more than happy to co-own this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant