github-project
Use when bootstrapping a repo (apply branch protection before first PR), PRs won't merge or BLOCKED, AI reviewer pushback, auto-merge fails for Dependabot/Renovate, branch protection or rulesets, CI fails, authoring or consuming reusable workflows, editing a repo's own .github/workflows, harden-runner, or CODEOWNERS/PR templates.
How do I install this agent skill?
npx skills add https://github.com/netresearch/github-project-skill --skill github-projectIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides a comprehensive suite of guides, templates, and automation scripts for managing GitHub projects securely. It includes tools for bootstrapping repository branch protection, auditing project structure, and hardening CI/CD pipelines. No malicious behavior or security risks were identified.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
GitHub Project Skill
When to Use
- Post
gh repo create+ push, before first PR — REQUIRED:scripts/init-branch-protection.sh OWNER/REPO - First issue/PR into a foreign repo —
references/upstream-contributions.mdBEFORE filing - Adding a workflow job — pitfall #6
- PR won't merge / threads
- Auto-merge fails (Dependabot/Renovate)
- Solo auto-approve
- Branch protection, rulesets
- GHA failures
- Signed-commit merge
- CodeQL
- Scorecard
- CODEOWNERS, templates, labels
- Fork PR merge base
Quick Diagnostics
PR Won't Merge
gh pr view PR --repo OWNER/REPO \
--json mergeStateStatus,reviewDecision,mergeable,reviewThreads
Solo Maintainer: Stuck on REVIEW_REQUIRED
First preserve the documented review contract (references/review-policy-contract.md). For an authorized solo-maintainer setup, either assets/pr-quality.yml.template (auto-approve, approvals >= 1) or scripts/init-branch-protection.sh OWNER/REPO --solo (approvals 0, conversation resolution kept) — references/auto-merge-guide.md compares both.
Auto-merge Setup
Requires allow_auto_merge, pull_request_target, bot detection, gh pr merge --auto (references/auto-merge-guide.md).
Auto-merge Not Working
gh pr view PR --repo OWNER/REPO --json autoMergeRequest --jq .autoMergeRequest
Bypass actors: references/security-config.md.
GitHub Actions Failing
gh run list --repo OWNER/REPO --limit 5
gh run view RUN_ID --repo OWNER/REPO --log-failed
gh run rerun RUN_ID --repo OWNER/REPO
"CI failed on main" can be a fork PR. A run's branch is the head branch, so a fork PR from a branch named main shows up as main in notifications and in gh run list --branch main. Its pull_requests array is empty. Before treating your main as red, read event and head_repository: pull_request from another repository is that PR's failure.
gh api repos/OWNER/REPO/actions/runs/RUN_ID \
--jq '{event, head_branch, head_repo: .head_repository.full_name}'
A failed scheduled run in a repository you do not own can still notify you. GitHub sends the notifications of a scheduled workflow to "the user who last modified the cron syntax in the workflow file" (schedule). A fork that carries your commits to that file therefore reports its failed schedules to you, and its runs name you as actor. Scheduled workflows start disabled in a fork of a public repository (disabling a workflow), so someone with access to the fork switched them on, and only such a user can switch them off again (admin: Settings → Actions; write access: gh workflow disable WORKFLOW --repo OWNER/FORK — without --repo it acts on the checkout's repository, which can be the upstream). Check the run's repository before you debug it: gh api repos/OWNER/FORK/actions/runs/RUN_ID --jq '{repo: .repository.full_name, event, actor: .actor.login}'.
Security Quick Checks
gh api repos/OWNER/REPO/rules/branches/main
gh api repos/OWNER/REPO/branches/main/protection \
--jq '{rcr: .required_conversation_resolution.enabled, admins: .enforce_admins.enabled}'
gh api repos/OWNER/REPO/code-scanning/default-setup --jq '.state'
gh pr view PR --repo OWNER/REPO --json reviewThreads --jq '.reviewThreads'
Merge Strategy Issues
references/auto-merge-guide.md: signed-commit rebase, workflow-file PRs, Copilot race.
Calling Organisation Reusables
Rule: uses: netresearch/<repo>/.github/workflows/<name>.yml@main. Never a commit hash, also not @<sha> # main; third-party actions stay SHA-pinned. A CodeQL actions/unpinned-tag, zizmor or SonarCloud finding on such a line is dismissed as won't fix, never fixed by pinning. Why: references/reusable-workflow-security.md.
Running Scripts
scripts/init-branch-protection.sh OWNER/REPO # baseline
scripts/init-branch-protection.sh OWNER/REPO --from-current-checks # after first CI
scripts/init-branch-protection.sh OWNER/REPO --merge-queue # then: org-standard queue
scripts/verify-github-project.sh /path/to/repository # local-checkout audit
No editorializing
State what a change does, not how good it is.
References
| Topic | Reference |
|---|---|
| Repo bootstrap | references/repo-bootstrap.md |
| Repository file layout | references/repository-structure.md |
| Branch migration | references/branch-migration.md |
| Repository retirement, Packagist abandon | references/repo-retirement.md |
| Dependabot/Renovate | references/dependency-management.md |
| Auto-approve + auto-merge | references/auto-merge-guide.md |
| Merge strategy | references/merge-strategy.md |
| Sub-issues | references/sub-issues.md |
| Release labeling | references/release-labeling.md |
| gh CLI commands | references/gh-cli-reference.md |
| Polyglot CI checklists | references/repo-setup-guide.md |
| Scorecard, CodeQL, security | references/security-config.md |
| Qualified human approvals, actual base, stacked PR guard | references/review-policy-contract.md |
| actionlint | references/actionlint-guide.md |
| Actions upgrades, Node-runtime wave | references/actions-upgrade-guide.md |
| Workflow bash pitfalls | references/workflow-bash-patterns.md |
| Runner capacity, concurrency groups (schedule vs push) | references/ci-runner-capacity.md, scripts/collect-runner-capacity.py |
| No editorializing | references/no-editorializing.md |
| Fork merge base | references/pr-commit-cleanup.md |
| Multi-repo batch ops | references/multi-repo-operations.md |
| Private copy of a public repo (mirror push) | references/multi-repo-operations.md |
| Cross-repo references, code permalinks | references/cross-repo-references.md |
| Foreign-repo contributions | references/upstream-contributions.md |
| Reusable workflow security | references/reusable-workflow-security.md |
| Reusable workflow pitfalls | references/reusable-workflow-pitfalls.md |
| Org security settings | references/org-security-settings.md |
| Tag validation | references/tag-validation.md |
| AI reviewer pushback | references/ai-reviewer-pushback.md |
| Agentic workflows | references/agentic-workflows.md |
| Pages + data collectors | references/pages-and-collector-workflows.md |
Contributing: https://github.com/netresearch/github-project-skill
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/netresearch/github-project-skill/github-project">View github-project on skillZs</a>