corp-new

Create, verify, and register private corp-* department repositories with GitHub and HQ.

215|26|Updated Dec 15, 2025

Search Tags:#automation #github #repository #registration #private #hq #corp

Ready to run

npx skills add https://github.com/serejaris/personal-corp-skills --skill corp-new

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: corp-new
Source: https://github.com/serejaris/personal-corp-skills/tree/main/skills/corp-new
Command: npx skills add https://github.com/serejaris/personal-corp-skills --skill corp-new

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Creating and maintaining private corp-* department repositories and a single HQ entry is error-prone and scattered across tools. This skill automates the end-to-end setup, verification, and registration to reduce manual overhead and ensure consistency.

Core Features & Use Cases

Normalize a department slug (corp-*) from domain labels and human-readable names.
Create, clone, or verify a local repository and corresponding private GitHub repo, including safe synchronization.
Register a single HQ row linking local path and GitHub URL to centralize governance and visibility.

Quick Start

Provide the department label, domain, owner, HQ file path, and local repos root to begin a dry-run and registration process.

Frequently Asked Questions about corp-new

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

FAQPage Schema

How do I automate creating a private GitHub repository for a department?▼

You can automate creating a private GitHub repository by providing a department label, domain, owner, and local repos root. The automation handles local repo setup, GitHub repository creation, safe synchronization, and enforces the private setting to ensure secure departmental source control.

What is the best way to register a department repository to a central HQ file?▼

The best way to register a department repository is to use an automated process that adds a single HQ row linking the local repository path and GitHub URL. This centralizes governance and visibility by connecting the HQ entry directly to the owner repository.

How do I normalize a department slug from a human-readable name for repository creation?▼

Normalizing a department slug involves converting domain labels and human-readable names into a standardized corp-* format. This ensures naming consistency across local repositories and GitHub before proceeding with creation, verification, or cloning operations.

Does this repository registration process include preflight checks before creating the GitHub repo?▼

Yes, the repository registration process includes preflight checks and explicit approval steps before creation. These checks verify the local repository and GitHub state, ensuring safe synchronization and preventing errors during the end-to-end setup of the private corp-* repository.

Can I run a dry-run before registering my private corp repository to HQ?▼

Yes, you can run a dry-run before registration by providing the department label, domain, owner, HQ file path, and local repos root. This allows you to verify the end-to-end setup and synchronization safely before committing the HQ entry.