codex-issue-digest

Generates headline-first digests of openai/codex GitHub issues by label and time window.

5|1|Updated Jun 26, 2026
One-click install
npx skills add https://github.com/looooonk/better-codex --skill codex-issue-digest-looooonk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-issue-digest
Source: https://github.com/looooonk/better-codex/tree/main/.codex/skills/codex-issue-digest
Command: npx skills add https://github.com/looooonk/better-codex --skill codex-issue-digest-looooonk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Product owners and maintainers of openai/codex need a fast way to see which bug reports and enhancement requests are gaining user attention, without manually scanning GitHub issues across many feature-area labels. ## Core Features & Use Cases - Label-scoped issue collection: Runs a Python collector via the GitHub CLI to gather bug and enhancement issues for specific owner labels (e.g., tui, exec, app) or across all labels. - Attention scoring: Counts unique human interactions (new issues, comments, reactions) within a configurable window and marks elevated items with fire markers scaled to the window length. - Headline-first reporting: Produces a summary-first digest with optional details tables, inline numbered issue references, and a compact source line citing script version, git head, and time window. - Use Case: A TUI owner asks for the digest of labels tui and exec over the past week and receives a headline naming the top user-surfaced issues with links, plus an optional details table. ## Quick Start Use $codex-issue-digest to run the Codex issue digest for labels tui and exec over the previous 24 hours.

Frequently Asked Questions about codex-issue-digest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a GitHub issue digest for openai/codex by label?▼

Run the collector script with the labels flag, for example: python3 .codex/skills/codex-issue-digest/scripts/collect_issue_digest.py --labels tui exec --window-hours 24. It returns JSON with summary inputs and digest rows used to write the report.

How do I summarize GitHub issues across all labels or a custom time window?▼

Pass --all-labels to scan bug and enhancement issues across every feature-area label, and use --window with values like "past week", "48h", or "7d" to change the lookback period from the default 24 hours.

What does the fire emoji attention marker mean in the digest?▼

The marker reflects unique human user interactions during the window: one fire for elevated attention (5 users over 24 hours) and two for very high attention (10 users). Thresholds scale linearly with longer or shorter windows, and bot activity is excluded.

Does the issue digest collector require the GitHub CLI?▼

Yes, the collector shells out to the gh command for search, issue, comment, and reaction API calls, so gh must be installed and authenticated. It also reads the current git head of the repo checkout for provenance reporting.

Why might a reaction-only issue be missing from the digest?▼

GitHub issue search is seeded by updated_at, so an issue that only received new reactions without comments or edits may not appear in search results. Covering those cases would require a persisted snapshot store or a broader label scan.