Skip to content

Feat: per-program capability check (Phase 3) #74

Description

@rubambiza

Part of #72 (Phase 3).

Per-program PAT-scope and label checks at invocation time, drawn from each skill's ## Requirements block.

Relationship to #39

This addresses the checks half of the repo-onboarding request in #39 (label presence + PAT-scope validation). The config/fork half of #39 (adding <owner>/<name> to the repo set and creating the fork) maps to Phase 2 (#73). #39 should be closed only once both halves land, so neither issue uses a closing keyword on #39 alone.

Scope

  • Each skill's SKILL.md: add a machine-readable ## Requirements block (explicit key-value, not prose).
  • scripts/repoman-check.sh (or inline per program): parse ## Requirements, check PAT scopes via gh auth status --json, check labels via gh label list --repo owner/name.

Not a universal gate

Checks run at invocation of the specific program, not at repo-add time. A repo can be enrolled without label write access; the check only fires when a program that needs labels runs against it. Additive: programs that do not call the check work exactly as today.

Assisted-By: Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestrepomanRepoMan multi-owner automation interface epic and sub-issues

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions