Skip to content

feat(skills-next): add sentry-get-started skill#235

Open
evanpurkhiser wants to merge 1 commit into
mainfrom
evanpurkhiser/feat-skills-next-add-sentry-get-started-skill
Open

feat(skills-next): add sentry-get-started skill#235
evanpurkhiser wants to merge 1 commit into
mainfrom
evanpurkhiser/feat-skills-next-add-sentry-get-started-skill

Conversation

@evanpurkhiser

Copy link
Copy Markdown
Member

Adds the sentry-get-started skill (first-error scope) along with its references.yml and only the non-SDK references it needs: concepts/errors.md, first-error-setup.md, new-project.md, and setup-verification.md. The SDK references this skill points at are delivered by the separate per-SDK PRs and the SDK reference organization PR.

First-error-scope skill plus the non-SDK references it needs; SDK references live in their own commits.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 08ea929. Configure here.


When it's done, surface other options — chiefly the **`sentry-instrument`** skill to add more
telemetry (tracing is the usual next step), and releases so issues tie to the deploy that introduced
them. Don't auto-run them.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing skill availability check

Medium Severity

After first-error setup, the skill tells agents to surface the sentry-instrument skill without checking the harness skill list. The existing-user menu requires that check before handoff, so follow-up routing can name a skill that is not installed.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 08ea929. Configure here.

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