CommunityRédaction et éditiongithub.com

getsentry/guide-ecriture-blog

Rédigez, révisez et améliorez des articles de blog pour le blog technique de Sentry en respectant les normes d'écriture, la voix et le niveau de qualité de Sentry.

Qu'est-ce que guide-ecriture-blog ?

Cette compétence est conçue pour assister les développeurs et rédacteurs techniques dans la création d'articles de blog destinés au blog technique de Sentry. Elle garantit que chaque article respecte les normes d'écriture spécifiques de Sentry, y compris le ton, la voix et les exigences de qualité. La compétence s'active dès que l'utilisateur mentionne des termes comme « article de blog », « brouillon de blog », « publication d'annonce », « article technique », « plongée en profondeur » ou « postmortem », ou demande de l'aide pour écrire sur un sujet technique lié à Sentry. Elle est compatible avec les plateformes d'IA agent comme Claude Code, Cursor et Codex. Le fonctionnement repose sur l'analyse du contenu existant ou des instructions de l'utilisateur pour produire, réviser ou améliorer des brouillons, en appliquant des règles éditoriales prédéfinies comme la structure des articles, l'utilisation d'exemples de code, la clarté technique et l'engagement du lecteur développeur.

Compatible avec~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/getsentry/skills/tree/main/skills/blog-writing-guide

Installed? Explore more Rédaction et édition skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

Documentation

Que fait guide-ecriture-blog ?

Rédigez, révisez et améliorez des articles de blog pour le blog technique de Sentry en respectant les normes d'écriture, la voix et le niveau de qualité de Sentry. Utilisez cette compétence chaque fois que quelqu'un demande de rédiger un article de blog, de préparer un article technique, de réviser un contenu de blog, d'améliorer un brouillon, de rédiger une annonce produit, de créer une plongée en profondeur technique, ou de produire tout contenu écrit destiné au blog de Sentry ou à son public de développeurs. Déclenchez-la également lorsque l'utilisateur mentionne « article de blog », « brouillon de blog », « rédaction », « publication d'annonce », « article technique », « plongée en profondeur », « postmortem », ou demande de l'aide pour la rédaction technique pour Sentry. Même si l'utilisateur dit simplement « aide-moi à écrire sur [fonctionnalité/sujet] » — si cela ressemble à quelque chose qui pourrait devenir un article de blog Sentry, utilisez cette compétence.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

getsentry/agents-md

Creates and maintains concise AGENTS.md and CLAUDE.md project instruction files. Use when asked to create AGENTS.md, update AGENTS.md, maintain agent docs, set up CLAUDE.md, document repository agent conventions, or keep coding-agent instructions minimal and reference-backed.

getsentry/brand-guidelines

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/claude-settings-audit

Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.

getsentry/code-simplifier

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

getsentry/commit

ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.

getsentry/create-branch

Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.

getsentry/django-access-review

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/django-perf-review

Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.

getsentry/doc-coauthoring

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/find-bugs

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/gha-security-review

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/gh-review-requests

Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member. Use when asked to "find PRs I need to review", "show my review requests", "what needs my review", "fetch GitHub review requests", or "check team review queue".

getsentry/iterate-pr

Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.

getsentry/presentation-creator

Create data-driven presentation slides using React, Vite, and Recharts with Sentry branding. Use when asked to "create a presentation", "build slides", "make a deck", "create a data presentation", "build a Sentry presentation". Scaffolds a complete slide-based app with charts, animations, and single-file HTML output.

getsentry/pr-writer

Create, refresh, and rewrite PR titles and descriptions following Sentry conventions. Use when opening a PR, writing or updating a PR title/body/description, refreshing an existing PR after material changes, or preparing branch changes for review.

getsentry/security-review

Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.

getsentry/skill-scanner

Scan agent skills for security issues. Use when asked to "scan a skill", "audit a skill", "review skill security", "check skill for injection", "validate SKILL.md", or assess whether an agent skill is safe to install. Checks for prompt injection, malicious scripts, excessive permissions, secret exposure, and supply chain risks.

getsentry/skill-writer

Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill", "synthesize sources into a skill", "improve a skill from positive/negative examples", "update a skill", or "maintain skill docs and registration". Handles source capture, precision passes, authoring, registration, and validation.

getsentry/sred-project-organizer

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

getsentry/sred-work-summary

Go back through the previous year of work and create a Notion doc that groups relevant links into projects that can then be documented as SRED projects.

Skills associés