corp-new

Solid

Use when creating, verifying, or registering a private corp-* department repository for a founder or company operating system, including local repo setup, GitHub repository creation or cloning, safe synchronization, and registration in an HQ Markdown file.

AI & Automation 176 stars 21 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
75
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Corp New Create or verify a private `corp-*` department repository and register it in a local HQ Markdown file. ## What The Skill May Change After approval, this skill may create a local folder, initialize git, create a private GitHub repository, clone an existing repository, commit a minimal README, push committed work, fetch from origin, and edit one HQ table row. Stop and ask for explicit approval after the dry-run summary before any create, clone, commit, push, or HQ edit. ## Configuration Resolve configuration in this order: explicit user request, environment variables, project instructions, then documented defaults. Required values from the user or project config: | Value | Env var | Default | |---|---|---| | Department label | `DEPARTMENT_LABEL` | ask the user | | Department domain | `DEPARTMENT_DOMAIN` | ask the user | | GitHub owner or org | `GITHUB_OWNER` | ask the user | | Local repositories root | `CORP_REPOS_ROOT` | `~/Documents/GitHub` | | HQ Markdown file | `HQ_FILE` | ask the user | | Repository prefix | `REPO_PREFIX` | `corp-` | Optional values: - `DEPARTMENT_TABLE_HEADING`: heading or marker near the department table. - `DEPARTMENT_SLUG`: explicit slug override. Ask before making changes if the department label, department domain, `GITHUB_OWNER`, or `HQ_FILE` cannot be resolved. Repositories are private by design; do not offer public visibility unless the user explicitly overrides the skill's safety model. ## Preflight Before creating or editi...

Details

Author
serejaris
Repository
serejaris/personal-corp-skills
Created
5 months ago
Last Updated
yesterday
Language
HTML
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Listed

github

GitHub repository operations — PRs, issues, releases, branch protection, CODEOWNERS, security settings. Use when user says 'review my PR', 'create a release', 'set up branch protection', 'add CODEOWNERS', 'audit repo settings', or asks about GitHub repo configuration.

7 Updated today
anmolnagpal
Code & Development Listed

github-repo-hardening

Audit GitHub repository governance and access control settings including branch protection rules, ruleset configuration, secret scanning, push protection, CODEOWNERS, signed commits, required reviews, and admin bypass policies. Use this skill whenever the user asks about branch protection, "is my main branch safe", required reviews, force-push prevention, CODEOWNERS, signed commits, gitsign, Sigstore, secret scanning, push protection, custom secret patterns, repo settings, ruleset vs branch protection, or merge queue. Trigger on phrases like "harden my repo", "audit my branch rules", "secret scanning", "CODEOWNERS review", "are my settings safe", "lock down main". Use this even when the user only mentions one of these sub-topics.

1 Updated 2 weeks ago
hlsitechio
Code & Development Listed

github-skill-publisher

Use this skill when the user wants to publish, update, package, document, or synchronize an agent skill to GitHub. It captures a single-skill-per-repository workflow, bilingual README writing style, GitHub repository creation, commit/push updates, publish readiness checks, Codex/Claude Code/OpenClaw compatibility checks, portability checks, and security review for public skill repositories.

1 Updated 1 weeks ago
chemny