Omar SobhandClaude Opus 4.7
7b23f61632
Hand-authored skill catalog anchored to real 2026-07 versions:
- Rust 1.97.1 (stable), edition 2024
- React 19.2.7, Server Components + Actions
- TailwindCSS 4.3.3 (CSS-first config, Oxide engine)
- three.js r185 (WebGPURenderer stable, BatchedMesh matured)
- React Native 0.86 / Expo SDK 54+ (New Architecture default)
- cargo-nextest 0.9.140, gitleaks 8.20+, cargo-audit 0.21+
- Postgres 17 (18 in beta, don't rely on)
- CUDA Blackwell, Metal Apple7+, ROCm CDNA3
Ships 15 skills across the categories:
foundation/ workspace-repo-commit-protocol
small-focused-commits
tdd-red-green-refactor
code-review-checklist
int-xx-marker-protocol
decompose-int-items
rust/ write-rust-current-edition
rust-error-handling
cargo-test-driven-development
rust-async-tokio-idioms
backend/ postgres-migrations-forward-only
postgres-index-selection
api-pagination-day-1
frontend/ react-19-server-components
tailwind-v4-idioms
component-4-state-model
mobile/ expo-managed-vs-bare
rn-flashlist-perf
gpu/ gpu-coalescing-and-occupancy
roofline-model
threejs/ threejs-perf-and-teardown
security/ cargo-audit-workflow
secret-scanning-gitleaks
skills_loader.rs walks skills/**/*.md, parses YAML frontmatter
(name, description, when_to_use, tags), upserts via
skills_catalog::upsert_builtin. Idempotent per boot — bumps version
+ appends skill_versions row ONLY when body changes. Deterministic
sha256-derived ids so builtins are stable across boots.
Dockerfile copies skills/ to /etc/clawmates/skills. Server boot
task spawns loader alongside team_template_loader.
Follow-ups (Slice 3.5c continuation, future PRs):
- 20-30 more skills (duckdb, shadcn composition, a11y, WebGPU
migration, metal frame capture, rocprof, deep gitea forge
integration, semgrep rulepacks)
- Bind skills to team template roles (add [role.skills] refs to
templates/teams/*.toml + wire template_role_skills population
in team_template_loader)
Co-Authored-By: Claude Opus 4.7 <[email protected]>
55 lines
2.3 KiB
Markdown
55 lines
2.3 KiB
Markdown
---
|
|
name: workspace-repo-commit-protocol
|
|
description: How to interact with /workspace/repo — the mission's checked-out codebase — and how to commit + push meaningful changes back.
|
|
when_to_use: You are a coder, committer, or any role that edits code. Pin this at turn start so you never lose orientation.
|
|
tags: [foundation, coding, git]
|
|
---
|
|
|
|
# Workspace repo + commit protocol
|
|
|
|
You are running inside a mission's team container. The clawhdf5/backend/whatever repository the mission targets is bind-mounted at **`/workspace/repo`**. That is the ONLY path where source-modifying edits belong.
|
|
|
|
## Ground rules
|
|
|
|
1. **`cd /workspace/repo` at the start of every substantive turn.** If you `pwd` and it isn't `/workspace/repo`, cd there first — your default CWD is the ZeroClaw agent workspace (`~/workspace`), which is scratch storage, not the codebase.
|
|
2. **All `file_read` / `file_write` / `shell` calls that touch source use paths under `/workspace/repo`.** Anything else is scratch — the mission will not persist it.
|
|
3. **Never write files outside `/workspace/repo` and expect them to survive** — the agent workspace resets, `/tmp` is per-container ephemeral.
|
|
|
|
## Commit protocol
|
|
|
|
When (and only when) you have a meaningful, tested change:
|
|
|
|
```
|
|
cd /workspace/repo
|
|
git status # sanity-check what you touched
|
|
git diff --stat # confirm scope matches the plan
|
|
git add -A
|
|
git commit -m "<INT-NN> <one-line title>
|
|
|
|
<one-paragraph rationale — WHY, not what>
|
|
|
|
Refs: INT-NN
|
|
"
|
|
git push
|
|
```
|
|
|
|
- **Commit message uses the mission's INT-XX marker** on the subject line — the mission's task-card parser (Slice 5) advances state on it.
|
|
- **One INT per commit** unless the change genuinely can't be split; split-when-in-doubt.
|
|
- **Never `--force`, never rewrite pushed history** without an explicit `HANDOFF: safe to force-push` from the reviewer.
|
|
|
|
## When NOT to commit
|
|
|
|
- Tests failing → fix or revert; never commit red.
|
|
- Reviewer emitted `REVIEW_BLOCK: INT-NN — <reason>` for the current item.
|
|
- The change is a WIP or exploratory — that lives in the agent's scratch workspace, not the repo.
|
|
|
|
## Emit the completion marker
|
|
|
|
After a successful push, on a line by itself:
|
|
|
|
```
|
|
COMPLETED: INT-NN
|
|
```
|
|
|
|
The mission loop advances on that marker. If you didn't push, don't emit it.
|