Skip to content

Demonstrate basectl gh issue readiness and basectl gh branch stale #196

Description

@codeforester

Summary

base-demo already follows an issue-first, worktree-based contribution workflow (per AGENTS.md) but doesn't demonstrate the two base v1.7.0 gh subcommands built for exactly that workflow.

Details

  • base v1.7.0 added basectl gh issue readiness (checks issue body sections, labels, assignees, and optional GitHub Project fields before assigning agentic implementation work) and basectl gh branch stale, per base's CHANGELOG.md [1.7.0] section, including stable JSON inspection envelopes for both.
  • base-demo's own AGENTS.md describes exactly the issue-branch-worktree workflow these commands support ("Create or choose a GitHub issue before implementation work," branch naming, worktree-per-PR), but neither command appears in README, docs, or .ai-context/.

Impact

These commands would let base-demo showcase Base's opinionated repo/issue hygiene tooling directly against its own already-documented contribution workflow — a concrete, self-referential demonstration that reinforces trust in the tool.

Suggested fix

Reference basectl gh issue readiness and basectl gh branch stale in AGENTS.md's workflow section and/or add a short example to docs/ or the demo showing them run against a base-demo issue/branch.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or product improvementneeds-demoChange should update a project demo

Type

No type

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions