Menu
Pre-commit review workflow to catch issues before they're committed
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Full Sentry SDK setup for Elixir. Use when asked to "add Sentry to Elixir", "install sentry for Elixir", or configure error monitoring, tracing, logging, or crons for Elixir, Phoenix, or Plug applications. Supports Phoenix, Plug, LiveView, Oban, and Quantum.
Configure specific Sentry features beyond basic SDK setup. Use when asked to monitor AI/LLM calls, set up OpenTelemetry pipelines, or create alerts and notifications.
Create a complete Sentry SDK skill bundle for any platform. Use when asked to "create an SDK skill", "add a new platform skill", "write a Sentry skill for X", or build a new sentry-<platform>-sdk skill bundle with wizard flow and feature reference files.
Fix production issues and review code with Sentry context. Use when asked to fix Sentry errors, debug issues, triage exceptions, review PR comments from Sentry, or resolve bugs.
Guide through complete workflow for adding a new RPC provider to Lasso
Quick check for docs that are out of sync with code
| name | review-changes |
| description | Pre-commit review workflow to catch issues before they're committed |
Comprehensive pre-commit review to ensure code quality, test coverage, and no regressions.
git status
git diff --stat
mix compile --warnings-as-errors
Zero compilation errors and zero warnings. Fix before committing.
mix test --exclude battle --exclude slow
All tests pass. No new failures.
mix credo --strict
Any new Credo issues? Fix design and readability issues at minimum.
git diff
Check for:
IO.inspect, IO.puts)If modifying providers: Adapter implements behaviour, tests cover validation, config updated.
If modifying request pipeline: Failover logic intact, circuit breaker correct, telemetry maintained.
If modifying WebSocket: Connection lifecycle handled, subscriptions multiplexed, gap-filling preserved.
If modifying configuration: Backward compatible, documented, validation updated.
PRE-COMMIT REVIEW
=================
FILES CHANGED:
[file list with +/- lines]
COMPILATION: PASS/FAIL
TESTS: PASS/FAIL (N/N in Xs)
CREDO: PASS/FAIL (N new issues)
CODE REVIEW: [notes]
CONTEXTUAL CHECKS: [if applicable]
OVERALL: READY TO COMMIT / NOT READY
SUGGESTED COMMIT MESSAGE:
-------------------------
[message]
If user says "fix it", can automatically:
IO.inspect, IO.puts in non-test code)mix format)Confirm before auto-fixing.