Phase 2 of the multi-skill build effort. Same 14-step pipeline as Phase 1.
## What landed
### New skill: engineering/kubernetes-operator
End-to-end Kubernetes Operator discipline. Published as BOTH:
- Standalone plugin: engineering/kubernetes-operator/
- Bundled mirror: engineering/skills/kubernetes-operator/
3 stdlib-only Python tools:
- crd_validator.py — checks CRD YAMLs for status subresource,
structural schema, conditions array, printer
columns, version policy, scope
- reconcile_lint.py — finds reconcile-loop bugs in Go: time.Sleep,
spec mutation via r.Update, missing requeue,
oversized reconcile bodies, panic/os.Exit,
unbalanced finalizer add/remove
- operator_capability_audit.py — scores against OperatorHub Capability
Levels 1-5 with concrete next-level steps
4 reference docs:
- operator_pattern.md — what an operator IS, when to use vs Helm/Deployment
- crd_design.md — anatomy of a production CRD, versioning, conversion
- reconcile_loop.md — idempotence patterns, error/requeue, status subresource
- tooling_landscape.md — controller-runtime / kubebuilder / operator-sdk /
metacontroller / KOPF / java-operator-sdk decision tree
Asset templates:
- crd_template.yaml — passes crd_validator.py PASS-clean
- reconcile_skeleton.go — passes reconcile_lint.py PASS-clean
Plus: SKILL.md (213 lines), README.md, /operator-audit slash command.
### Audit verdict (evidence-based)
Closest existing coverage:
- engineering-team/senior-devops — kubectl / blue-green deploys, no operators
- engineering/helm-chart-builder — Helm charts (different abstraction)
- engineering-team/cloud-security — k8s RBAC at high level
None cover the Operator pattern (CRD + controller + reconcile loop).
Verdict: BUILD. Gap is real and tooling-shaped.
### Self-test (meta-validation)
During build, the new linters caught 4 real bugs in their own asset templates:
- crd_validator.py wrongly anchored regexes to start-of-line, misclassifying
indented YAML keys (scope, singular, listKind) as missing
- reconcile_lint.py checked finalizer add/remove balance per-function,
missing the cross-function pattern in the asset (Add in main reconcile,
Remove in reconcileDelete)
Both linters fixed; assets re-tested; both PASS clean.
This is Karpathy principle 4 in action: verifiable goals catch real bugs.
### Marketplace / registry
- marketplace.json: kubernetes-operator registered as standalone plugin
- engineering-advanced-skills bundle: 45 → 46 → 47 skills, version → 2.4.1
- engineering/.claude-plugin/plugin.json: version + skill list updated
- mkdocs.yml: nav entry under "Engineering - POWERFUL"
- docs/skills/engineering/kubernetes-operator.md: docs page (manual,
pending generate-docs.py classification fix)
- docs/commands/operator-audit.md: auto-generated
- .codex/, .gemini/: synced
### Karpathy-coder gates
- complexity_checker (strict): 85/100 average, depth-4-to-6 WARNs (lambdas
in capability audit). Same range as karpathy-coder's own scripts (70/100
baseline). Verdict: WARN, not FAIL.
- All 1648 tests pass (was 1630; added 18 for the new skill).
- mkdocs build --strict: succeeded in 14.44s.
### Verifiable success criteria (all green)
✓ scripts/*.py --help → exit 0 for all 3 scripts
✓ SKILL.md frontmatter → name + description + tags + compatible_tools
✓ plugin.json schema → 8 fields exact (verified by check_plugin_json.py)
✓ sync_skill_bundles → standalone ↔ bundled mirror in sync
✓ marketplace.json → standalone entry + bundle counts updated
✓ generate-docs.py → command page generated (skill page manual)
✓ mkdocs build --strict → succeeded
✓ cross-tool sync → codex + gemini synced
✓ pytest tests/ → 1648 passed, 0 failed
✓ CHANGELOG.md → [Unreleased] entry expanded
✓ Self-test → linters caught + fixed 4 real bugs in own assets
## Files
- engineering/kubernetes-operator/ (new standalone plugin)
- engineering/skills/kubernetes-operator/ (new bundled mirror)
- commands/operator-audit.md (new slash command)
- docs/skills/engineering/kubernetes-operator.md (new docs page)
- docs/commands/operator-audit.md (auto-generated)
- mkdocs.yml (nav entries)
- .claude-plugin/marketplace.json (registered)
- engineering/.claude-plugin/plugin.json (bundle bumped)
- CHANGELOG.md ([Unreleased] expanded)
- .codex/, .gemini/ (cross-tool sync)
https://claude.ai/code/session_01Dq12xJakFRxwaoU8Pqejdm
6 KiB
| title | description |
|---|---|
| Slash Commands — AI Coding Agent Commands & Codex Shortcuts | 31 slash commands for Claude Code, Codex CLI, and Gemini CLI — sprint planning, tech debt analysis, PRDs, OKRs, and more. |
:material-console: Slash Commands
31 commands for quick access to common operations
-
:material-console:{ .lg .middle }
/a11y-audit
Scan a frontend project for WCAG 2.2 accessibility issues, show fixes, and optionally check color contrast.
-
:material-console:{ .lg .middle }
/changelog
Generate Keep a Changelog entries from git history and validate commit message format.
-
:material-console:{ .lg .middle }
/code-to-prd
Reverse-engineer a frontend codebase into a complete Product Requirements Document.
-
:material-console:{ .lg .middle }
/competitive-matrix
Build competitive matrices with weighted scoring, gap analysis, and market positioning insights.
-
:material-console:{ .lg .middle }
/financial-health
Analyze financial statements, build valuation models, assess budget variances, and construct forecasts.
-
:material-console:{ .lg .middle }
/flag-cleanup
Run the full feature-flag cleanup workflow:
-
:material-console:{ .lg .middle }
/focused-fix
Systematically repair an entire feature or module using the 5-phase protocol. Target: $ARGUMENTS (a feature path or m...
-
:material-console:{ .lg .middle }
/google-workspace
Google Workspace CLI administration via the gws CLI. Run setup diagnostics, security audits, browse and execute recip...
-
:material-console:{ .lg .middle }
/karpathy-check
Review your staged changes (or last commit) against Karpathy's 4 coding principles.
-
:material-console:{ .lg .middle }
/okr
Generate cascaded OKR frameworks from company-level strategy down to team-level key results.
-
:material-console:{ .lg .middle }
/operator-audit
Run the full audit on a Kubernetes Operator repository:
-
:material-console:{ .lg .middle }
/persona
Generate structured user personas with demographics, goals, pain points, and behavioral patterns.
-
:material-console:{ .lg .middle }
/pipeline
Detect project stack and generate CI/CD pipeline configurations for GitHub Actions or GitLab CI.
-
:material-console:{ .lg .middle }
/plugin-audit
Full audit pipeline for any skill, plugin, agent, or command in this repository. Runs 8 validation phases, auto-fixes...
-
:material-console:{ .lg .middle }
/prd
Generate a concise product requirements document for a feature, initiative, or problem statement.
-
:material-console:{ .lg .middle }
/project-health
Generate portfolio health dashboards and risk matrices for project oversight.
-
:material-console:{ .lg .middle }
/retro
Analyze retrospective data for recurring themes, sentiment trends, and action item effectiveness.
-
:material-console:{ .lg .middle }
/rice
Prioritize features using RICE scoring (Reach, Impact, Confidence, Effort) with optional capacity constraints.
-
:material-console:{ .lg .middle }
/saas-health
Calculate SaaS financial health metrics from raw business numbers, benchmark against industry standards, and project ...
-
:material-console:{ .lg .middle }
/seo-auditor
Systematically scan, audit, and optimize documentation files for SEO. Targets README.md files and docs/ pages — fixes...
-
:material-console:{ .lg .middle }
/sprint-health
Score sprint health across delivery, quality, and team metrics with velocity trend analysis.
-
:material-console:{ .lg .middle }
/sprint-plan
Create a sprint plan with prioritized stories and capacity guardrails.
-
:material-console:{ .lg .middle }
/tc
Dispatch a TC (Technical Change) command. Arguments: $ARGUMENTS.
-
:material-console:{ .lg .middle }
/tdd
Generate tests, analyze coverage, and validate test quality using the TDD Guide skill.
-
:material-console:{ .lg .middle }
/tech-debt
Scan codebases for technical debt, score severity, and generate prioritized remediation plans.
-
:material-console:{ .lg .middle }
/user-story
Generate structured user stories with acceptance criteria, story points, and sprint capacity planning.
-
:material-console:{ .lg .middle }
/wiki-ingest
Ingest a new source into the LLM Wiki. This is the most-used command.
-
:material-console:{ .lg .middle }
/wiki-init
Bootstrap a new LLM Wiki vault. Creates raw/, wiki/{entities,concepts,sources,comparisons,synthesis}, the index and l...
-
:material-console:{ .lg .middle }
/wiki-lint
Health-check the wiki. Surfaces orphan pages, broken wikilinks, stale claims, missing frontmatter, contradictions, an...
-
:material-console:{ .lg .middle }
/wiki-log
Show recent entries from wiki/log.md. Every LLM operation on the wiki leaves a standardized entry:
-
:material-console:{ .lg .middle }
/wiki-query
Ask the wiki a question. The librarian reads index.md first, picks relevant pages across categories, synthesizes an a...