Debug Production Failures With Evidence
Production failures can be difficult to trace across errors, releases, logs, and affected users. This skill organizes the investigation and verification into seven steps.
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "debug-production" from https://skillstore.io/skills/logbrewco-debug-production.md and its manifest at https://skillstore.io/api/skills/logbrewco-debug-production/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Utilisation de « debug-production ». Why did checkout fail after the release?
RĂ©sultat attendu:
Observed: Checkout errors began with the latest release. Inferred: A missing discount object may be the cause. Unknown: Other affected routes.
Utilisation de « debug-production ». Did the deployed fix stop the errors?
RĂ©sultat attendu:
Verification: No recurrence was observed after deployment. This is supporting evidence, not proof, and depends on the observed traffic.
The static findings reflect Markdown formatting, documented LogBrew endpoints, and ordinary incident investigation text. No evidence of malicious instructions or unauthorized data transfer was found in the reviewed files.
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
https://skillstore.io/skills/logbrewco-debug-production/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/logbrewco-debug-production?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/logbrewco-debug-production?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/logbrewco-debug-production/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/logbrewco-debug-production.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>logbrewco. (2026). debug-production security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/logbrewco-debug-production/audits/1@techreport{logbrewco-logbrewco-debug-production-2026,
author = {logbrewco},
title = {debug-production security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/logbrewco-debug-production/audits/1},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "debug-production security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "logbrewco"
date-released: "2026-10-27"
url: "https://skillstore.io/skills/logbrewco-debug-production/audits/1"
identifiers:
- type: other
value: "skillstore:logbrewco-debug-production:audit:1"
description: "Skillstore immutable audit report identifier"
Trace a production error from the matching issue to relevant logs and traces.
Compare the first occurrence and release with the failing source frame.
Review recurrence and traffic after deployment and report remaining uncertainty.
Investigate this production error using the supplied stack trace and logs: [evidence].
Investigate failures in [approved project] for [service] during [time window]. Summarize observed facts and unknowns.
Compare the first occurrence and release for [issue]. Inspect the relevant trace and propose a tested fix if evidence supports it.
Investigate [issue], record the baseline occurrence, and assess [deployment] after traffic returns. Report recurrence, evidence limits, and unresolved questions.
Auteur
logbrewcoLicence
MIT
RĂ©vision Skillstore
r1
Avis de version
Lâauteur nâa dĂ©clarĂ© aucune version.
RĂ©f
07bd35e828bc5e79e3fd7ad19a1298e33cdbb753
RĂ©cence de maintenance
27/10/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
Verify Release Health After Deployment
Release decisions can be difficult when error counts and traffic change together. Compare release evidence and receive a Go, Rollback, or Wait recommendation.
Instrument Your App with LogBrew
Application errors and logs can be difficult to trace across deployments. This skill configures LogBrew instrumentation and checks that a test event can be read back.
Ajouter des patterns dâobservabilitĂ© Python
par 0xDarkMatter
Les services Python manquent souvent de patterns cohérents pour la journalisation, les métriques et le traçage. Cette compétence fournit des exemples pratiques avec structlog, Prometheus et OpenTelemetry pour les applications de production.
RĂ©soudre plus rapidement les incidents DevOps
par sickn33
Les incidents de production nĂ©cessitent un triage rapide entre les journaux, les mĂ©triques, les traces et les plateformes cloud. Cette compĂ©tence guide le dĂ©bogage DevOps structurĂ©, lâanalyse des causes racines et la planification de la reprise.
Diagnostiquer les erreurs de production
par sickn33
Les erreurs de production peuvent ĂȘtre difficiles Ă retracer Ă travers les logs, les services et les alertes. Cette compĂ©tence guide lâinvestigation structurĂ©e, lâanalyse des causes racines et les Ă©tapes de rĂ©ponse aux incidents.
EnquĂȘter plus vite sur les erreurs
par sickn33
Les erreurs de production se cachent souvent dans les logs, les traces de pile et les changements récents. Cette skill aide Claude, Codex et Claude Code à structurer les preuves et à prioriser les causes probables.
Instrumenter les applications Azure avec Application Insights
par microsoft
Ajouter une tĂ©lĂ©mĂ©trie fiable aux applications hĂ©bergĂ©es sur Azure peut ĂȘtre difficile selon les frameworks et les modĂšles de dĂ©ploiement. Cette compĂ©tence fournit des conseils concis de configuration dâApplication Insights, des rĂ©fĂ©rences SDK et des modĂšles de configuration Azure.
CrĂ©er des dossiers de commandement dâincident gouvernĂ©s
par yaojingang
Les notes dâincident manquent souvent de clartĂ© sur la sĂ©vĂ©ritĂ©, la responsabilitĂ© et la communication adaptĂ©e Ă chaque public. Cette skill transforme les preuves opĂ©rationnelles en un dossier gouvernĂ© pour la rĂ©ponse, la revue et le suivi.