Skip to content

chore(skills-next): remaining unorganized skills-next content#268

Merged
evanpurkhiser merged 1 commit into
mainfrom
evanpurkhiser/chore-skills-next-remaining-unorganized-skills-next-content
Jul 9, 2026
Merged

chore(skills-next): remaining unorganized skills-next content#268
evanpurkhiser merged 1 commit into
mainfrom
evanpurkhiser/chore-skills-next-remaining-unorganized-skills-next-content

Conversation

@evanpurkhiser

Copy link
Copy Markdown
Member

No description provided.

@evanpurkhiser evanpurkhiser requested a review from sergical July 9, 2026 19:37
Comment thread skills-next/references/search-query-language.md Outdated
Comment thread skills-next/references/search-query-language.md Outdated
Comment thread skills-next/references/search-query-language.md Outdated
Comment thread skills-next/references/search-query-language.md Outdated
@evanpurkhiser evanpurkhiser force-pushed the evanpurkhiser/chore-skills-next-remaining-unorganized-skills-next-content branch from 4f37d63 to 457be0c Compare July 9, 2026 20:24
Comment on lines +93 to +94
Identity & grouping: `issue` (short code, e.g. `SENTRY-ABC`), `issue.category` (`error`,
`performance`, `frontend`, `outage`), `issue.type` (e.g.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bug: The documentation for issue.category lists frontend and outage as valid values, but these are not supported by Sentry.
Severity: MEDIUM

Suggested Fix

Update the documentation to replace the incorrect values frontend and outage with the correct list of Sentry issue categories: error, performance, feedback, replay, and cron.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: skills-next/references/search-query-language.md#L93-L94

Potential issue: The documentation file `search-query-language.md` incorrectly lists
`frontend` and `outage` as valid values for the `issue.category` search filter. The
actual valid values are `error`, `performance`, `feedback`, `replay`, and `cron`. This
discrepancy will cause systems or users, particularly AI agents relying on this
documentation, to construct invalid search queries, leading to failed searches.

Did we get this right? 👍 / 👎 to inform future reviews.

@evanpurkhiser evanpurkhiser merged commit 824c342 into main Jul 9, 2026
18 checks passed
@evanpurkhiser evanpurkhiser deleted the evanpurkhiser/chore-skills-next-remaining-unorganized-skills-next-content branch July 9, 2026 20:40
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.

2 participants