Menú
Creates a GitHub repository for the website project, initializes git, and pushes the code.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Build and deploy a production-ready Trust Center for any company. Use this skill whenever someone asks to create a trust center, compliance portal, security page, or wants to publish their SOC 2/SOC 3/ISO 27001/HIPAA/compliance posture publicly. Also triggers when someone mentions gated document access for audit reports, NDA-based document sharing, or wants to replace paid trust center tools like Secureframe, Vanta, Drata, or SafeBase. Even if they just say "I need a place to share my SOC 2 with customers" — that's a trust center. Use this skill.
NIST Cybersecurity Framework v2.0 expert. Reference-depth knowledge of the six Functions (Govern, Identify, Protect, Detect, Respond, Recover), Categories and Subcategories, Profiles (Current vs Target), Tiers, Implementation Examples, and the practitioner workflow of using CSF as a board-readable cybersecurity outcomes language. Backed by the SCF crosswalk for control-by-control mechanics.
Verbatim reference for all 320 NIST 800-171A Rev 2 assessment objectives, plus the Rev 2 → Rev 3 control crosswalk. Use for AO-level lookups (e.g., 3.1.1[c]), evidence planning, and forward-mapping to Rev 3. Pairs with cmmc-expert.
CMMC v2.0 expert for DoD contractors. Covers NIST 800-171 Rev 2 (14 families, 110 controls), SPRS scoring, POA&M rules, 32 CFR Part 170, DFARS clauses, scoping, ESP/CSP, C3PAO assessment lifecycle, and Rev 2 → Rev 3 transition.
Interpret testssl-inspector normalized findings, recommend remediations, and tie evidence back to SCF anchor controls plus SOC 2 / NIST 800-53 r5 / PCI DSS 4.0.1 / ISO 27002:2022 equivalents derived from SCF crosswalks.
Scaffolds a complete React/Vite website project from site-config.json. Generates components, styles, and configuration based on the site type and plan data.
| name | website-repo |
| description | Creates a GitHub repository for the website project, initializes git, and pushes the code. |
| allowed-tools | Bash, Read, Write, Edit, Glob |
You are running the /grc-portfolio:repo skill. Your job is to create a GitHub repository for the website project and push the code.
Find site-config.json:
$ARGUMENTS for a project directory pathRead it and validate that status.buildComplete === true. If not, tell the user to run /grc-portfolio:build first.
Check that gh CLI is installed and authenticated:
gh --version
gh auth status
If not installed, tell the user to run:
brew install gh
gh auth login
Ask the user:
projectName from config)Check if .gitignore exists in the project directory. If not, create one:
# Dependencies
node_modules/
# Build output
dist/
# Environment variables
.env
.env.local
.env.production
# OS files
.DS_Store
Thumbs.db
# IDE
.vscode/
.idea/
# Logs
*.log
npm-debug.log*
# Lambda packages
lambda/*.zip
If it exists, verify it includes at least node_modules, dist, .env, .env.local, and .DS_Store. If any of those entries are missing, add them before staging any files — git add -A will happily stage .env.local with secrets in it otherwise.
cd <projectDir>
git init
Before staging, confirm .env* files are ignored:
git check-ignore -q .env .env.local 2>/dev/null && echo "ok: env files ignored"
If that fails (exit code 1), stop and fix .gitignore — do not run git add -A until env files are ignored.
git add -A
# Sanity check: nothing under .env* should be staged.
if git diff --cached --name-only | grep -E '^\.env(\.|$)'; then
echo "ERROR: env file staged — unstage it and fix .gitignore" >&2
exit 1
fi
git commit -m "Initial commit: scaffolded GRC portfolio website"
gh repo create <repoName> --<visibility> --source . --push
This creates the repo on GitHub, sets the remote, and pushes the code.
Get the repo URL and owner:
gh repo view --json url,owner
Update site-config.json:
github.repoName to the repo namegithub.repoUrl to the full URLgithub.owner to the owner logingithub.visibility to public/privatestatus.repoCreated = trueTell the user:
<github.repoUrl>/grc-portfolio:infra next (if not done) or /grc-portfolio:cicd to set up continuous deployment$ARGUMENTS = arguments passed after /repo (expected: project directory path)