Browsing:

getsentry

Take a list of projects and their related documentation, and organize them into the SRED format for submission.

getsentry

Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.

getsentry

Alias for sentry-skills:skill-writer. Use when users explicitly ask for skill-creator or reference the legacy skill name. Redirects to the canonical skill authoring workflow.

getsentry

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

getsentry

Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.

getsentry

Django access control and IDOR security review. Use when reviewing Django views, DRF viewsets, ORM queries, or any Python/Django code handling user authorization. Trigger keywords: IDOR, access control, authorization, Django permissions, object permissions, tenant isolation, broken access.

getsentry

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

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.

affaan-m

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

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).