CommunityProductivité et collaborationgithub.com

getsentry/agents-md

Crée et maintient des fichiers d'instructions de projet concis AGENTS.md et CLAUDE.md. Utilisez-le lorsqu'on vous demande de créer AGENTS.md, mettre à jour AGENTS.md, maintenir la documentation de l'agent, configurer CLAUDE.md, documenter les conventions d'agent du dépôt ou garder les instructions de l'agent de codage minimales et basées sur des références.

Qu'est-ce que agents-md ?

Cette compétence permet de générer et de maintenir de manière fiable les fichiers AGENTS.md et CLAUDE.md, essentiels pour diriger les agents de codage (comme Claude Code, Cursor ou Copilot). Son principal intérêt est de remplacer une documentation volumineuse et potentiellement obsolète par des instructions concises et structurées, directement exploitables par l'agent à chaque début de session. Elle prend en charge les workflows standard des dépôts, les conventions de projet et les références aux fichiers de code ou de documentation existants. L'agent, guidé par ce fichier, peut ainsi comprendre en un coup d'œil la pile technique, les commandes clés, les tests et les règles de contribution, ce qui améliore considérablement la pertinence et la précision de ses actions.

Compatible avec✓Claude Code~Codex CLI~Cursor
Part ofAgent Workflows
npx skills add https://github.com/getsentry/skills/tree/main/skills/agents-md

Installed? Explore more Productivité et collaboration skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

Voir l'original→Voir toutes les compétences

Demander à votre IA préférée

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

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Documentation

Que fait agents-md ?

Crée et maintient des fichiers d'instructions de projet concis AGENTS.md et CLAUDE.md. Utilisez-le lorsqu'on vous demande de créer AGENTS.md, mettre à jour AGENTS.md, maintenir la documentation de l'agent, configurer CLAUDE.md, documenter les conventions d'agent du dépôt ou garder les instructions de l'agent de codage minimales et basées sur des références.

Utilisation

Lorsqu'un utilisateur vous demande de configurer ou de mettre à jour la documentation d'agent pour un dépôt, utilisez cette compétence pour générer ou mettre à jour un fichier AGENTS.md (ou CLAUDE.md) à la racine du dépôt.

Format recommandé

  • Titre et brève description du projet
  • Pile technique et dépendances principales
  • Workflows standard (construction, test, lint)
  • Conventions de projet (structure, style de codage, messages de commit)
  • Références clés vers les fichiers de documentation, de code ou de test pertinents
  • Commandes shell courantes pour l'exécution, les tests et le débogage

Comportement typique

  1. Lister les fichiers importants du dépôt (package.json, go.mod, etc.)
  2. Identifier les scripts de construction et de test
  3. Résumer les conventions de contribution et de code
  4. Mettre l'accent sur les instructions minimales, mais suffisantes, orientées vers les références
  5. Ne pas dupliquer des informations déjà mises à jour dans d'autres fichiers de documentation

Exemple de sortie (AGENTS.md minimal)

# MyProject

- **Stack**: Node.js, TypeScript, Express
- **Build** : `npm run build`
- **Test** : `npm test`
- **Lint** : `npm run lint`
- **Conventions** : Prettier, ESLint, commit conventionnel
- **Références** : `./docs/architecture.md`, `./CONTRIBUTING.md`

Mises en garde

  • Ne pas inclure de fichiers ou de secrets sensibles.
  • Documenter de manière à ce que l'agent puisse se référer à d'autres fichiers sans avoir à les lire en entier.
  • Garder les instructions personnelles (comme CLAUDE.md) séparées des instructions partagées par l'équipe (comme AGENTS.md).

Individual skills in this repo

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

getsentry/blog-writing-guide

Write, review, and improve blog posts for the Sentry engineering blog following Sentry's 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/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

steipete/gemini

Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.

community

steipete/gh-issues

Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.

community

steipete/skill-creator

Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.

community

steipete/clawhub

Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.

community

steipete/coding-agent

Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.

community

steipete/mcporter

List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.

community
← More Productivité et collaboration skills