github-project-provisioninglisted

# GitHub Project Provisioning ## Safety contract - Start with `inspect` or `plan`. Neither command may mutate GitHub or tracked files. - Never run `apply` until the user explicitly approves the displayed plan and exact target. - Re-display the authenticated account, owner, repositories, Project title, and every planned mutation before approval. - Treat mismatched identity, target, config digest, state digest, missing permissions, and duplicate names as hard failures. - Do not delete, rename, archive, or silently repair views/workflows. - Do not create a live Organization Project while merely authoring or testing this skill. - `--confirm-target` prevents target mix-ups; it is not an authorization mechanism. Human approval remains a host-level interaction requirement. The content-derived `plan_id` prevents an approved plan file from being edited before apply. ## Prerequisites - Install the complete `github-operations` plugin. A copied skill directory is intentionally unsupported. - Require Python 3.11+, `gh`, an authenticated GitHub account, and Project scopes. - Use an explicit config or `.agents/github-operations.json` at the current git root. Read [the config contract](references/config.md) before creating one. ## Workflow Resolve `scripts/run.py` against this skill directory before executing it; do not run a bare relative path from the target repository's working directory. 1. Inspect the target and authentication read-only: ```bash python3 <skill-dir>/scripts