configure-workflow

Configures and audits GitHub repositories for the github-workflow skill's Project boards, labels, and rulesets.

1|1|Updated Aug 2, 2026
One-click install
npx skills add https://github.com/blac9216/waypoint --skill configure-workflow-blac9216
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: configure-workflow
Source: https://github.com/blac9216/waypoint/tree/main/.claude/skills/configure-workflow
Command: npx skills add https://github.com/blac9216/waypoint --skill configure-workflow-blac9216

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Setting up a GitHub repository to work with the github-workflow skill requires many exact fixtures — a Project board with specific fields and views, a canonical label set, branch rulesets, account grants, and docs/process files — and any drift breaks the workflow. This Skill creates those fixtures, audits them for drift, and captures an edited Project as the new standard. ## Core Features & Use Cases - Apply mode: Runs a ten-step ordered setup covering the Project board, collaborator and Project admin grants, canonical plus area labels, docs/process scaffolding, branch rulesets, an optional reviewer account, and skill propagation. - Audit mode: A read-only check that verifies every fixture is present and exact, exiting non-zero with a gap list when labels drift, rulesets are missing, or docs/process markers are unfilled. - Capture mode: Snapshots an owner-edited Project (fields, options, views, workflows) into manifests/project.json so the next repository gets the new standard. - Use Case: After adopting the github-workflow skill on a new repository, run the apply flow to provision the board, labels, and branch protections idempotently, then re-run the audit any time someone edits the Project by hand. ## Quick Start Ask the agent to configure this repository for the github-workflow skill, providing the Project owner login and project number.

Frequently Asked Questions about configure-workflow

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

FAQPage Schema
How do I configure a GitHub repository for an automated issue workflow?▼

Run the apply flow, which provisions the Project board fields and views, the canonical label set plus repo area labels, branch rulesets, account grants, and docs/process files in a fixed order. It is idempotent, so re-running it is safe.

How do I audit GitHub Project and label configuration drift?▼

Run scripts/audit.sh with the owner login, project number, and automation account. It is read-only, checks labels, Project fields and views, grants, rulesets, docs/process files, and skill copies, and exits non-zero listing every gap.

Can GitHub Project workflows and view group-by be set via the API?▼

No. Project workflows and view group-by/sort exist only in the GitHub UI, so the scripts print a checklist for the owner to apply manually. Workflows are readable, so the audit can still verify they are enabled.

Why do the scripts fail with bad substitution on macOS?▼

The scripts require bash 4 or newer for case-folding parameter expansion, but macOS ships bash 3.2 as /bin/bash. Install a newer bash (for example via brew) and invoke the scripts with that binary; _lib.sh enforces this with a named error.

What are the limitations of managing GitHub Projects with the gh CLI?▼

The automation account cannot create Projects on personal accounts, cannot read or write rulesets without admin, and ProjectV2 exposes no queryable field for a named collaborator's role, so admin grants are re-asserted unconditionally and reported as unknown in audits.