engineering-github-repo-standards

Apply GitHub repository standards and security settings via the gh CLI.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/scanady/nexus-skills --skill engineering-github-repo-standards-scanady
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-github-repo-standards
Source: https://github.com/scanady/nexus-skills/tree/main/skills/engineering-github-repo-standards
Command: npx skills add https://github.com/scanady/nexus-skills --skill engineering-github-repo-standards-scanady

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually configuring branch protection, security features, access controls, and standard file artifacts across GitHub repositories is repetitive and error-prone. This Skill applies a consistent, opinionated repository baseline directly through the gh CLI, with file artifacts delivered as a single pull request. ## Core Features & Use Cases - Direct settings application: Configures merge policy, branch protection on main and develop, Dependabot, secret scanning, push protection, CodeQL, and Actions permissions via gh api calls. - Profiles and contexts: Supports four profiles (standard, collaborative, monorepo, regulated) and two contexts (internal org repos, external personal repos), with guards against invalid combinations. - Artifact pull request: Opens one PR from chore/apply-github-standards containing CODEOWNERS, SECURITY.md, CONTRIBUTING.md, issue templates, a PR template, a CodeQL workflow, and dependabot.yml. - Use Case: Ask the agent to standardize all repos matching service-* in your org with the regulated profile; it discovers current settings, confirms a plan, applies the changes, and opens one artifact PR per repo. ## Quick Start Ask the agent to standardize the GitHub repo my-org/api-service with the standard profile using the gh CLI.

Frequently Asked Questions about engineering-github-repo-standards

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

FAQPage Schema
How do I apply branch protection rules to multiple GitHub repos at once?▼

Pass a comma-separated list or glob pattern such as service-* as the repo input. The skill iterates per repo, applies profile-scaled protection rules to main and develop via gh api, and opens one artifact PR per repo with an aggregated summary.

What GitHub security settings does this skill configure?▼

It enables Dependabot alerts and security updates, private vulnerability reporting, secret scanning with push protection, and a CodeQL workflow on every repo. GitHub Advanced Security is attempted only for the regulated profile and skipped gracefully without an Enterprise license.

What permissions and gh CLI version are required?▼

You need gh CLI 2.28 or higher, authenticated via gh auth login, with admin permission on every target repo. External context requires repo and workflow scopes; internal context additionally requires admin:org and write:org for team grants.

Can I preview the changes before anything is applied?▼

Yes, set dry-run to true and the skill prints every intended gh api call without performing any writes, branch creation, or PRs. It also always shows discovered settings and a confirmation plan before any write operation.

Why can't I use the regulated profile on a personal repository?▼

The regulated profile requires org-level features such as team-based access and GitHub Advanced Security, so it is restricted to internal context. The skill blocks the external plus regulated combination with an error before any API call.

What happens if the artifact pull request already exists?▼

The skill checks for an open PR from the chore/apply-github-standards branch before creating one. If found, it updates the existing PR with gh pr edit instead of failing on a duplicate creation attempt.