try-works/role-model / .agents/skills/recursive-mode
recursive-mode
UnverifiedRepository workflow orchestration skill for staged implementation, locked artifacts, late-phase receipts, and durable memory maintenance. Use when executing recursive-mode runs, resuming a run, locking a phase, or verifying locks.
docs/templates/commands/check-reusable-repo-hygiene.md
View on GitHub# check-reusable-repo-hygiene
> Maintainer-facing check for reusable workflow/skill repos that should not ship recursive run residue.
## Usage
```powershell
python "<SKILL_DIR>/scripts/check-reusable-repo-hygiene.py" --repo-root .
pwsh -NoProfile -File "<SKILL_DIR>/scripts/check-reusable-repo-hygiene.ps1" -RepoRoot .
```
Optional strict cleanliness check:
```powershell
python "<SKILL_DIR>/scripts/check-reusable-repo-hygiene.py" --repo-root . --require-clean-git
pwsh -NoProfile -File "<SKILL_DIR>/scripts/check-reusable-repo-hygiene.ps1" -RepoRoot . -RequireCleanGit
```
## What It Checks
- `/.recursive/run/` contains only `.gitkeep`
- no concrete `/.recursive/run/<run-id>/` references remain in committed text files
- no concrete temp-directory residue remains in committed text files
- no generated local residue such as `__pycache__/`, `*.pyc`, `.pytest_cache/`, `.mypy_cache/`, or `.ruff_cache/` remains in the repo tree
- the packaged bootstrap workflow template at `references/bootstrap/RECURSIVE.md` exists and matches `/.recursive/RECURSIVE.md`
- optional `git status --porcelain` cleanliness when `--require-clean-git` is selected
Interpretation:
- default mode: repo-content hygiene only
- `--require-clean-git`: final handoff check for a reusable skill/workflow repo snapshot
Use this before calling a reusable skill/workflow repo clean.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |