log-analyzelisted
Install: claude install-skill TomasLicek/ai
<purpose>
Capture a bug in the project's `pm/backlog/` with zero ceremony. The script
auto-detects which of two backlog layouts the project uses and does the right
thing for each. Your job is only to produce good content (a sharp title, a
one-line summary, a clear problem).
**State-folder backlog (maildir style, e.g. VinRaptor).** Detected when
`pm/backlog/0-inbox/` exists. Raw drops live in state folders and `backlog.md`
is GENERATED, never hand-edited. The script:
1. Writes a standalone `bug-<slug>.md` into `0-inbox/` (the only raw-drop
path — the express lane was retired 2026-08-08; urgency is a
`**Priority:**` header line now, see `--priority` in usage).
2. Runs the repo's `bin/backlog-index` to regenerate `backlog.md`. No bullet is
inserted by hand. Index regen is best-effort - a failure warns but the bug
file still lands and the run still succeeds.
**Legacy flat backlog.** The historical two-part convention, so the entry is
indistinguishable from a hand-written one:
1. A standalone `bug-<slug>.md` file (Title + Type/Status/Source line +
`## Problem` + optional `## Repro`).
2. A linked one-line bullet under `## Bugs` in `backlog.md`, placed before the
`## Decisions` section.
A pure bash + awk script does the deterministic file plumbing.
</purpose>
<the_script>
`~/.claude/skills/log-analyze/scripts/bug.sh`
Pure bash + awk (no Python). It finds `pm/backlog/` by walking up from the
current directory, then picks a mode by whether `0-inbox/` exists th