Menú
Source code management workflow - nothing is ever lost
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
Automated quality check loops with escalation and fix sub-agents
JSON-based end-to-end test format, runner, and mock provider
Jujutsu (jj) skill for the ikigai project
How to write effective Ralph goals for Ikigai-driven workflows
Create and manage Ralph goals from Ikigai using the real ralph-pipeline scripts
Create repositories using the real ralph-pipeline repo-create script
| name | scm |
| description | Source code management workflow - nothing is ever lost |
jj workflow for preserving all work. Nothing is ever lost.
Every change is automatically tracked. In jj, working copy (@) is always a commit. No staging area. Every save is part of the current commit.
Commit after every testable change - After each TDD cycle, run jj commit -m "msg". Don't batch. Worktree gets squash-merged anyway.
Finalize before destructive ops - Before jj restore, jj abandon, or ending session: commit first.
Experiments: commit, try, backout - Commit the experiment, evaluate, then jj backout -r @- if discarding. History preserved.
Unknown changes: preserve first - Never jj restore unknown changes. Commit checkpoint, then investigate with jj diff -r @-.
Deleting code: commit, then delete - Checkpoint before removing so you can recover from history.
jj edit away| Don't | Do Instead |
|---|---|
jj restore without thinking | Commit first |
jj abandon without checking | Verify commit is unwanted |
| Batch changes in one commit | Commit after each testable change |
| Leave session without finalizing | Commit before stopping |