harness-bootstrap
Skill0 starsChanged 7 months agoMITView on GitHub
Use when a repository needs the reusable docs harness installed or refreshed. Trigger when the user wants issue tracking docs, learning-note templates, playbooks, or role-based documentation folders added to a new or existing Codex project.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- lumatic2/askewly-harnesstheir own version, first seen Aug 21, 2026
- Synthenova/skillstheir own version, first seen Apr 22, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- lumatic2/askewly-harness★ 1same name
- Synthenova/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- decision-recordingSkill
- issue-driven-workflowSkill
- planning-workflowSkill
- review-workflowSkill
- spec-writingSkill
- subagent-workflowSkill
- technical-learning-noteSkill
- troubleshooting-workflowSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
If the repo already had conflicting docs, decide whether --force is appropriate.
- Distinctive: line 28
After bootstrap, encourage the user to create the first issue doc before larger implementation work.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Harness Bootstrap
Install the reusable docs harness into a target repository and leave the repository ready for issue-first, explainable Codex work.
When to use it
- a repo has no docs harness yet
- a repo wants
docs/issues,docs/learning,docs/playbooks, and related templates - a repo wants a reusable bootstrap instead of copying docs by hand
Workflow
- Confirm the target repository path.
- Run
scripts/init_harness.py <target-repo>. - Review created files and skipped files.
- If the repo already had conflicting docs, decide whether
--forceis appropriate. - Adjust project-specific text after bootstrap instead of editing templates directly.
Notes
- The bootstrap script copies templates only; it does not modify code.
- Existing files are preserved unless
--forceis used. - After bootstrap, encourage the user to create the first issue doc before larger implementation work.
Resources
- See
references/bootstrap-checklist.mdfor a short post-install checklist.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.