Sentry Skills

getsentry

Write, review, and improve blog posts for the Sentry engineering blog following Sentrys specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions blog post, blog draft, write-up, announcement post, engineering post, deep dive, postmortem, or asks for help with technical writing for Sentry. Even if the user just says help me write about [feature/topic] — if it sounds like it could become a Sentry blog post, use this skill.

getsentry

GitHub Actions security review for workflow exploitation vulnerabilities. Use when asked to review GitHub Actions, audit workflows, check CI security, GHA security, workflow security review, or review .github/workflows/ for pwn requests, expression injection, credential theft, and supply chain attacks. Exploitation-focused with concrete PoC scenarios.

getsentry

ALWAYS use this skill when creating or updating pull requests — never create or edit a PR directly without it. Follows Sentry conventions for PR titles, descriptions, and issue references. Trigger on any create PR, open PR, submit PR, make PR, update PR title, update PR description, edit PR, push and create PR, prepare changes for review task, or request for a PR writer.

getsentry

Warden skill: evaluates first-pass findings and proposes deterministic lint rules that could permanently catch the same patterns. Requires Wardens multi-pass pipeline (phase 2).