Agent Skill
2/7/2026

log-observability-issues

Run /check-observability, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-observability instead if you want to fix issues immediately.

P
phrazzld
1GitHub Stars
1Views
npx skills add phrazzld/codex-config

SKILL.md

Namelog-observability-issues
DescriptionRun /check-observability, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-observability instead if you want to fix issues immediately.

name: log-observability-issues description: | Run /check-observability, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-observability instead if you want to fix issues immediately.

/log-observability-issues

Run observability audit and create GitHub issues for all findings.

What This Does

  1. Invoke /check-observability to audit monitoring infrastructure
  2. Parse findings by priority (P0-P3)
  3. Check existing issues to avoid duplicates
  4. Create GitHub issues for each finding

This is an issue-creator. It creates work items, not fixes. Use /fix-observability to fix issues.

Process

1. Run Primitive

Invoke /check-observability skill to get structured findings.

2. Check Existing Issues

gh issue list --state open --label "domain/observability" --limit 50

3. Create Issues

For each finding:

gh issue create \
  --title "[P0] No error tracking configured" \
  --body "$(cat <<'EOF'
## Problem
No error tracking (Sentry) configured. Production errors are invisible.

## Impact
- Errors happen silently
- Users affected without our knowledge
- No alert when things break
- Debugging requires log diving

## Suggested Fix
Run `/fix-observability` or manually:
```bash
pnpm add @sentry/nextjs
npx @sentry/wizard@latest -i nextjs

Configure DSN in environment variables.


Created by /log-observability-issues EOF )"
--label "priority/p0,domain/observability,type/chore"


### 4. Issue Format

**Title:** `[P{0-3}] Observability gap description`

**Labels:**
- `priority/p0` | `priority/p1` | `priority/p2` | `priority/p3`
- `domain/observability`
- `type/chore`

**Body:**
```markdown
## Problem
What monitoring/logging is missing

## Impact
What goes unseen, risk of blind spots

## Suggested Fix
Commands or skill to run

---
Created by `/log-observability-issues`

Priority Mapping

GapPriority
No error trackingP0
No health endpointP0
Error tracking misconfiguredP1
No structured loggingP1
Shallow health checksP1
No alertingP1
No analyticsP2
Console.log overuseP2
No uptime monitoringP2
Performance monitoringP3

Output

After running:

Observability Issues Created:
- P0: 2 (no error tracking, no health endpoint)
- P1: 3 (logging, alerting, deep health)
- P2: 2 (analytics, console cleanup)
- P3: 1 (perf monitoring)

Total: 8 issues created
View: gh issue list --label domain/observability

Related

  • /check-observability - The primitive (audit only)
  • /fix-observability - Fix observability gaps
  • /observability - Full observability setup
  • /groom - Full backlog grooming
Skills Info
Original Name:log-observability-issuesAuthor:phrazzld