Sentry Issue Fix Loop
tixl3d/tixl
Walks through open Sentry issues for the tooll3 project, latest first, proposing a fix for each and committing them one at a time with your review between.
Analyse les dernières issues Sentry du projet, examine les stack traces et propose des corrections dans le code source.
Install Sentry Issues
$ npx skills add SocialGouv/code-du-travail-numerique --skill sentry-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SocialGouv/code-du-travail-numerique sentry-issues --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/SocialGouv/code-du-travail-numerique.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/sentry-issues .claude/skills/sentry-issues && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sentry-issues" agent skill from https://github.com/SocialGouv/code-du-travail-numerique/tree/dev/.claude/skills/sentry-issues into .claude/skills/sentry-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-issues", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/SocialGouv/code-du-travail-numerique/tree/dev/.claude/skills/sentry-issuesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add SocialGouv/code-du-travail-numerique --skill sentry-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SocialGouv/code-du-travail-numerique sentry-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SocialGouv/code-du-travail-numerique.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/sentry-issues .agents/skills/sentry-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sentry-issues" agent skill from https://github.com/SocialGouv/code-du-travail-numerique/tree/dev/.claude/skills/sentry-issues into .agents/skills/sentry-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-issues", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SocialGouv/code-du-travail-numerique --skill sentry-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SocialGouv/code-du-travail-numerique sentry-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SocialGouv/code-du-travail-numerique.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/sentry-issues .cursor/skills/sentry-issues && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sentry-issues" agent skill from https://github.com/SocialGouv/code-du-travail-numerique/tree/dev/.claude/skills/sentry-issues into .cursor/skills/sentry-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-issues", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/SocialGouv/code-du-travail-numerique.git --path .claude/skills/sentry-issues--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add SocialGouv/code-du-travail-numerique --skill sentry-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SocialGouv/code-du-travail-numerique sentry-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SocialGouv/code-du-travail-numerique.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/sentry-issues .gemini/skills/sentry-issues && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sentry-issues" agent skill from https://github.com/SocialGouv/code-du-travail-numerique/tree/dev/.claude/skills/sentry-issues into .gemini/skills/sentry-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-issues", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install SocialGouv/code-du-travail-numerique sentry-issuesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add SocialGouv/code-du-travail-numerique --skill sentry-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SocialGouv/code-du-travail-numerique.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/sentry-issues .github/skills/sentry-issues && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sentry-issues" agent skill from https://github.com/SocialGouv/code-du-travail-numerique/tree/dev/.claude/skills/sentry-issues into .github/skills/sentry-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-issues", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SocialGouv/code-du-travail-numerique --skill sentry-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SocialGouv/code-du-travail-numerique sentry-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SocialGouv/code-du-travail-numerique.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/sentry-issues .opencode/skills/sentry-issues && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sentry-issues" agent skill from https://github.com/SocialGouv/code-du-travail-numerique/tree/dev/.claude/skills/sentry-issues into .opencode/skills/sentry-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-issues", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sentry-issues- GitHub stars
- 122
- Token cost
- ~1.3k tokens
- SKILL.md length
- 528 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Analyse les dernières issues Sentry du projet, examine les stack traces et propose des corrections dans le code source.
- Works in 9 steps: Récupérer le token → Valider le projet → Récupérer les N dernières issues non… → …
- Tasks that involve Debugging
- SKILL.md covers Configuration, Arguments, Étapes and Bonnes pratiques
- Reaches sentry2.fabrique.social.gouv.fr; needs SENTRY_AUTH_TOKEN
What it does
Sentry Issues is an agent skill from SocialGouv/code-du-travail-numerique. Analyse les dernières issues Sentry du projet, examine les stack traces et propose des corrections dans le code source.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging. It works with Sentry. The repository describes itself as: Code du Travail Numérique. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Debugging
Example prompts
- “/sentry-issues”
Requirements
- A credential in SENTRY_AUTH_TOKEN
- Pre-approved tools (allowed-tools): Bash, Read, Edit, Grep, Glob, Agent
Workflow steps
9 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1454fab. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadEditGrepGlobAgent
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
sentry2.fabrique.social.gouv.fr
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
SENTRY_AUTH_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sentry Issues loads about 1.3k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 528 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Edit, Grep, Glob, Agent
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from SocialGouv/code-du-travail-numerique at commit 1454fab, republished under its Apache-2.0 licence (© SocialGouv). 528 words, ~1,250 tokens.
Download SKILL.mdSave it as
.claude/skills/sentry-issues/SKILL.md (or your agent's skills folder).- name
- sentry-issues
- description
- Analyse les dernières issues Sentry du projet, examine les stack traces et propose des corrections dans le code source.
- allowed-tools
- Bash, Read, Edit, Grep, Glob, Agent
- argument-hint
- [nombre d'issues (défaut: 10)] [--assign] [--comment <PR_URL>] [--fix]
Analyse des issues Sentry
Tu es un agent spécialisé dans l'analyse des erreurs Sentry pour le projet Code du travail numérique.
Configuration
- Sentry URL :
https://sentry2.fabrique.social.gouv.fr - Organisation :
incubateur - Projet :
fabnum-code-du-travail-numerique - Token : utilise la variable d'environnement
SENTRY_AUTH_TOKEN. Si elle n'est pas définie, demande le token à l'utilisateur avant de continuer. Ne jamais le lire depuis un fichier de config. - Frontend :
packages/code-du-travail-frontend/
Arguments
$ARGUMENTSpeut contenir :- Un nombre d'issues à récupérer (défaut : 10)
--assign: assigner les issues à l'utilisateur courant après analyse--comment <PR_URL>: ajouter un commentaire sur chaque issue avec le lien vers la PR--fix: proposer et appliquer des corrections dans le code source
Étapes
1. Récupérer le token
Vérifie si la variable d'environnement SENTRY_AUTH_TOKEN est définie :
echo "${SENTRY_AUTH_TOKEN:-NOT_SET}"- Si elle est définie, utilise-la pour tous les appels API.
- Si elle n'est PAS définie (
NOT_SET), demande à l'utilisateur de fournir son token Sentry (Auth Token commençant parsntryu_). Attends sa réponse avant de continuer. Ne tente PAS de le lire depuis un fichier.
2. Valider le projet
Appeler l'API GET /api/0/projects/ pour lister les projets et confirmer que fabnum-code-du-travail-numerique existe.
3. Récupérer les N dernières issues non résolues
GET /api/0/projects/incubateur/fabnum-code-du-travail-numerique/issues/?query=is:unresolved&sort=date&limit={N}Pour chaque issue, afficher : ID, titre, culprit (route), niveau, nombre d'occurrences, première/dernière apparition.
4. Récupérer les stack traces
Pour chaque issue pertinente (ignorer les titres minifiés sauf si on peut récupérer le message original) :
GET /api/0/issues/{issue_id}/events/latest/Extraire :
- Le type et message de l'exception
- Les frames de la stack trace (en priorité ceux marqués
inApp: true) - Les breadcrumbs d'erreur
- Les tags (URL, browser, OS)
5. Analyser et catégoriser
Classer chaque issue dans une catégorie :
- Hydration mismatch : chercher
Math.random(),generateUUID(),Date.now(),typeof window,usePathname()sans garde dans le code source - ChunkLoadError : erreur de cache après redéploiement
- 404 bruyantes :
Sentry.captureMessageoucaptureExceptionappelés pour des pages non trouvées - Erreurs externes : scripts tiers (iframes, CDN) en échec
- Bugs applicatifs : vraies erreurs dans le code métier (destructuration, null pointer, etc.)
- Code obsolète en cache : erreurs sur du code qui n'existe plus dans le source actuel
Show full SKILL.md (205 more words)Show less
6. Proposer des corrections (si --fix)
Pour chaque issue identifiée comme corrigeable :
- Localiser le fichier source correspondant via
GrepetGlob - Lire le fichier pour comprendre le contexte
- Proposer une correction avec
Edit - Expliquer le raisonnement
Corrections types :
- Remplacer
Math.random()/uuid()dans le rendu SSR par des IDs déterministes - Supprimer les
captureMessage/captureExceptionpour les 404 - Ajouter un auto-reload sur
ChunkLoadErrordans le error boundary - Ajouter des gardes null/undefined avant destructuration
- Améliorer le contexte des
captureException(ajouterextra)
7. Commenter les issues (si --comment <PR_URL>)
Pour chaque issue, ajouter un commentaire via :
POST /api/0/issues/{issue_id}/notes/
{"text": "Fix en cours dans la PR <PR_URL>\n\nCause : <explication>\nFix : <description du fix>\n\n-> A passer en fixed après merge et release."}8. Assigner les issues (si --assign)
Récupérer l'ID utilisateur courant via les notes existantes sur une issue :
GET /api/0/issues/{issue_id}/notes/Puis assigner :
PUT /api/0/issues/{issue_id}/
{"assignedTo": "user:{user_id}"}9. Produire un rapport
Afficher un tableau récapitulatif :
| # | Issue | Occurrences | Catégorie | Action | Statut |
|---|
Bonnes pratiques
- Ne jamais hardcoder le token dans le code ou les fichiers de config du projet
- Si
SENTRY_AUTH_TOKENn'est pas défini, toujours demander le token à l'utilisateur - Privilégier
jqpour parser le JSON (plus concis et lisible). Sijqn'est pas disponible, utiliserpython3en fallback - Toujours vérifier le code HTTP des réponses API
- Ne pas créer de commit automatiquement, laisser l'utilisateur décider
- Lancer les recherches de code en parallèle avec des agents
Explorepour la performance
© SocialGouv, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/sentry-issues of SocialGouv/code-du-travail-numerique.
Open the folder on GitHubat commit 1454fab
Compare with similar skills
Sentry Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sentry Issues this skillSocialGouv/code-du-travail-numerique | 122 | — | ~1.3k | Automated safety check: Notes | Apache-2.0 | |
| Sentry Issue Fix Looptixl3d/tixl | 5.1k | — | ~2.1k | Automated safety check: Notes | MIT | |
| Sentrymitsuhiko/agent-stuff | 3.2k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Sentry Auditqianyumeng0228/ShizukuX | 115 | — | ~490 | Automated safety check: Pass | Apache-2.0 | |
| Production Error Huntdifferent-ai/openwork | 24k | — | ~803 | Automated safety check: Pass | Custom licence | |
| Debug With Sentrysuperset-sh/superset | 15k | — | ~828 | Automated safety check: Pass | Custom licence |
Similar skills
Sentry
mitsuhiko/agent-stuff
Fetch and analyze Sentry issues, events, transactions, and logs.
Sentry Audit
qianyumeng0228/ShizukuX
Fetches unresolved Sentry issues and maps stack traces to local codebase for ShizukuPlus.
Production Error Hunt
different-ai/openwork
Traces an opaque production error in an OpenWork build to its cause using local server logs and Sentry, names the regressing PR and files a report.
Debug With Sentry
superset-sh/superset
Root-cause a production error with Sentry's evidence before touching code — pull the issue, read the stack trace and breadcrumbs, and separate the crash from its trigger.
- Official
Sentry Fix Issues
getsentry/sentry-for-ai
Find and fix issues from Sentry using MCP. An agent skill from getsentry/sentry-for-ai.
More from SocialGouv/code-du-travail-numerique
Tracking Plan
SocialGouv/code-du-travail-numerique
Rédige/actualise le plan de tracking Matomo métier (events/TRACKINGPLAN.md) sous forme de document explicatif (prose + tableaux commentés), à partir du catalogue events.extracted.json et du code…
Related
Works with
Categories
Questions about Sentry Issues
What does Sentry Issues do?
Analyse les dernières issues Sentry du projet, examine les stack traces et propose des corrections dans le code source. Sentry Issues is an agent skill from SocialGouv/code-du-travail-numerique. Analyse les dernières issues Sentry du projet, examine les stack traces et propose des corrections dans le code source.
When should I use Sentry Issues?
Sentry Issues fits situations like: tasks that involve Debugging.
How do I install Sentry Issues in Claude Code?
Run `npx skills add SocialGouv/code-du-travail-numerique --skill sentry-issues -a claude-code`. Or copy the skill folder (.claude/skills/sentry-issues in SocialGouv/code-du-travail-numerique) into .claude/skills/sentry-issues in your project. Claude Code loads it when a task matches its description.
How do I install Sentry Issues in Codex?
Run `npx skills add SocialGouv/code-du-travail-numerique --skill sentry-issues -a codex`. Or copy the skill folder (.claude/skills/sentry-issues in SocialGouv/code-du-travail-numerique) into .agents/skills/sentry-issues in your project. Codex loads it when a task matches its description.
Can I use Sentry Issues in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SocialGouv/code-du-travail-numerique --skill sentry-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sentry-issues, .gemini/skills/sentry-issues, .github/skills/sentry-issues and .opencode/skills/sentry-issues in your project.
What does Sentry Issues need to run?
Going by SKILL.md and its folder, Sentry Issues needs credentials named SENTRY_AUTH_TOKEN. Our summary lists: A credential in SENTRY_AUTH_TOKEN. Its frontmatter pre-approves these tools: Bash, Read, Edit, Grep, Glob, Agent.
Does Sentry Issues access the network?
SKILL.md names 1 domain. In commands or code: sentry2.fabrique.social.gouv.fr; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Sentry Issues safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Sentry Issues use?
Sentry Issues is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sentry Issues use?
About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sentry Issues?
Skills that share tags, products or a category with Sentry Issues: Sentry Issue Fix Loop (tixl3d/tixl, 5.1k stars), Sentry (mitsuhiko/agent-stuff, 3.2k stars), Sentry Audit (qianyumeng0228/ShizukuX, 115 stars) and Production Error Hunt (different-ai/openwork, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sentry Issues?
SocialGouv (a GitHub organization) maintains it in SocialGouv/code-du-travail-numerique, which has 122 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.
Source: SocialGouv/code-du-travail-numerique on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.