ops-journal
par mariusfit
Coding Agents & IDEsRésumé
Structured operational journal that captures deployments, incidents, changes, and decisions.
Description
Ce que fait ce skill
A command-line ops journal that logs deployments, incidents, configuration changes, and decisions to a local SQLite database. Supports incident lifecycle management with open/resolve tracking, timeline reconstruction, and exportable postmortem reports.
Keeps a structured, searchable record of operational events in a single local database rather than scattered across chat logs, tickets, or memory.
Quand l'utiliser
- Tracking what changed before an outage
- Reconstructing a timeline for a postmortem
- Searching past deployments by category or date
- Generating a weekly ops digest for a team
- Exporting incident history to a spreadsheet
Exemple de workflow
User asks: What happened during the API latency incident last week?
- 1
Run
python3 scripts/journal.py incident list --status resolvedto find the incident ID - 2
Run
python3 scripts/journal.py timeline INC-001to reconstruct the event sequence - 3
Run
python3 scripts/journal.py search --category incident --since 7dto surface related entries - 4
Export the timeline with
python3 scripts/journal.py timeline INC-001 --format markdown
Markdown timeline showing when the incident opened, all logged events during the window, and the recorded root cause and resolution
Installation
clawhub install mariusfit/ops-journalExécute la commande CLI, ou colle l'instruction dans Claude Code, Cursor, Codex ou l'agent de code que tu utilises.