known-issues-batch

Plan the next small batch of bug fixes from docs/phases/known-issues.md — pick a few Open rows that need no decision (default 4), confirm them and the release with the owner, number it as the next undefined phase (or straight after the active one), then write docs/phases/phase-N.M.md in the style of Phases 52.1 and 52.2, add the ROADMAP row and section and the spec.md §13 entry, mark the rows Scheduled and log any open questions. Plans only; /next-phase builds it. Run with /known-issues-batch, optionally with a count or the rows to take.

What does this entry provide?

known-issues-batch is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Plan a batch of known-issues fixes The known-issues log holds more open rows than one phase should take on. This skill takes **a few** of them, the smallest t. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding known-issues-batch to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.

Snapshot facts

Source: GitHub Skill Search
Quality: 58/100
Install method: codex
Repo: gwpreston16/Logbook
Repo updated: Oct 28, 2026

Install command

codex skill install gwpreston16/Logbook

Install method: codex

Review the upstream source before running this command.

GitHub project

Quality

Repo stars

Repo updated

Unknown

How is this score calculated?

Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.

Security signals

Scan coverage: Install metadata and the indexed document body.

Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.

Discovery note

# Plan a batch of known-issues fixes The known-issues log holds more open rows than one phase should take on. This skill takes **a few** of them, the smallest that need no decision

Report an issue with this listing