feat: /create-repository

.github/pull_request_template.md

@@ -0,0 +1,11 @@
+<!-- What problem does it solve or what feature does it add? -->
+## Overview
+
+<!-- Summarize the key changes in the Pull Request. -->
+## Key Changes
+- TBD: 1st key change of the PR
+- TBD: 2nd key change of the PR
+
+<!-- Add attached issue that this PR solves. -->
+## Related
+Closes #issue_number

README.md

@@ -77,6 +77,7 @@ its purpose, trigger phrases, and full instructions.
 
 | Skill                                                | Description                                                                                                                         |
 |------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|
+| **[create-repository](./skills/create-repository/)** | Creates and configures a GitHub repository under AbsaOSS (open source) or absa-group (internal). Runs a short interview, then shows an annotated `gh` command plan and executes it on confirmation — visibility, naming, admins, CODEOWNERS, labels, merge settings, and project links. |
 | **[pr-review](./skills/pr-review/)**                 | Pull request code review — reviews diffs for risk, security issues, API contract changes, dependency bumps, CI/CD and infrastructure changes. Produces concise Blocker / Important / Nit comments. |
 | **[tdd-workflow](./skills/tdd-workflow/)**           | Test-driven development: upfront SPEC.md planning + confirmation gate (avoids batch design), then vertical-sliced implementation (one test → one code cycle at a time, not all tests then all code). |
 | **[test-data-management](./skills/test-data-management/)** | Test data setup and management — factory functions, parametrised tests, deterministic seeds, fixture reuse, and production-data rules for unit and integration tests. |

docs/README.md

@@ -25,6 +25,7 @@ Navigation hub for all guides in this repository. Browse by category below.
 
 | Guide | Description |
 |----|----|
+| [Create Repository](./create-repository.md) | Creating a new AbsaOSS/absa-group repo from the template with standard guardrails |
 | [PR Review](./pr-review.md)             | How the PR review skill works, what sections it applies, and how to trigger it     |
 | [TDD Workflow](./tdd-workflow.md)       | Test-driven development with: specification, confirmation gates, and vertical-sliced implementation |
 | [Test Data Management](./test-data-management.md)   | How the test-data-management skill works, what it covers, and when it fires |

docs/create-repository.md

@@ -0,0 +1,69 @@
+# Create Repository Skill
+
+The `create-repository` skill creates and configures a brand-new GitHub repository under the Absa
+organizations — **AbsaOSS** (open source) or **absa-group** (internal) from the shared
+`cps-repository-template`. It applies the standard Absa CPS guardrails so every new repo starts consistent.
+
+---
+
+## What it does
+
+It runs a short interactive flow and never makes changes until you confirm:
+
+**interview → plan → confirm once → execute → report**
+
+| Phase | What happens                                                                                                  |
+|-------|---------------------------------------------------------------------------------------------------------------|
+| Interview | Asks a fixed set of short questions (visibility, name, admins, code owners, labels, auto-delete, project link) |
+| Plan | Shows the exact annotated `gh` commands it will run                                 |
+| Confirm | You approve the plan once                                                                                     |
+| Execute | Runs the approved commands verbatim, best-effort                                                              |
+| Report | Prints a results table with the repo URL and what was copied from the template                                |
+
+The repo is created from `absa-group/cps-repository-template`, which brings a README, CONTRIBUTING,
+and the `.github/` folder (workflows, dependabot, issue/PR templates, and an empty CODEOWNERS).
+
+Template link: [absa-group/cps-repository-template](https://github.com/absa-group/cps-repository-template)
+c
+---
+
+## What it always applies
+
+| Item | OSS (`AbsaOSS`) | Internal (`absa-group`) |
+|------|-----------------|--------------------------|
+| Created from `cps-repository-template` | ✓ | ✓ |
+| Apache-2.0 license | ✓ | — (proprietary) |
+| Populated CODEOWNERS | ✓ | — (template's empty file) |
+| Standard Absa label taxonomy | ✓ | ✓ |
+| Core Branches ruleset | ✓ | ✓ |
+| Auto-delete branches on merge | ✓ | ✓ |
+| Custom properties | — | ✓ |
+| Project link(s) | — (cross-org not allowed) | optional |
+
+---
+
+## How to trigger it
+
+Ask to create a repository. You don't have to say "repository" explicitly:
+
+> "Create a new open-source repo under AbsaOSS called telemetry-exporter."
+> "Spin up a repo for internal use called event-gate."
+> "Set up a new codebase under absa-group."
+
+It does **not** activate for modifying an existing repo (adding a single label, creating branches, PRs,
+issues, or workflow files, or cloning).
+
+---
+
+## Notes
+
+- Requires an authenticated GitHub CLI (`gh auth status`) as a member of the target org with permission
+  to create repositories. The orgs enforce SAML SSO — if a call is rejected mid-run, the skill keeps your
+  answers and tells you how to authorize and resume.
+- If a step fails, the skill reports it and prints the commands to finish the steps manually.
+
+---
+
+## Installation
+
+See [Getting Started](./getting-started.md) for the full install guide.

skills/create-repository-workspace/trigger-eval.json

@@ -0,0 +1,18 @@
+[
+  {"query": "spin up a new github repo under AbsaOSS for our new data-gateway service, public, I'll be admin", "should_trigger": true},
+  {"query": "I need a new project/codebase set up in absa-group for internal billing reconciliation", "should_trigger": true},
+  {"query": "make me a repo called schema-standards and add the standard ABSA labels", "should_trigger": true},
+  {"query": "scaffold a repository for the aquasec scan results, open source", "should_trigger": true},
+  {"query": "we're starting a new microservice, can you create the github repo and set codeowners + auto-delete branches", "should_trigger": true},
+  {"query": "new internal repo, link it to absa-group project 88 and make asmith admin", "should_trigger": true},
+  {"query": "create a repository for EventGate under our org", "should_trigger": true},
+  {"query": "set up a fresh repo with our recommended label taxonomy and an admin", "should_trigger": true},
+  {"query": "create an issue for the login bug in our api repo", "should_trigger": false},
+  {"query": "open a pull request from my feature branch", "should_trigger": false},
+  {"query": "create a new branch called feature/auth in this repo", "should_trigger": false},
+  {"query": "clone the absa-group/data-platform repo locally", "should_trigger": false},
+  {"query": "add a new label called hotfix to this existing repo", "should_trigger": false},
+  {"query": "init a git repo in my current local folder", "should_trigger": false},
+  {"query": "give bob admin access to our existing payments repo", "should_trigger": false},
+  {"query": "create a new GitHub Actions workflow file in the repo", "should_trigger": false}
+]