o8-contribute
Skill59 starsChanged 43 days agoMITView on GitHub
Work on repository issues, pull requests, commits, packet scope, or CLI and visual-proof references.
The file
Files
Contributions
Core authority is defined in AGENTS.md.
- For issues and pull requests, load the GitHub standard once. Public artifacts describe the mechanic without adding private identities, machine details, credentials, billing notes, or internal routing notes. Scan logs and screenshots before posting. Do not silently rewrite already-published material or Git history to remove a prior disclosure; escalate it.
- In packet worktrees, stay inside packet scope and use
o8 packet commit. Outside packets, use a focused Conventional Commit and one pull request per issue. Implementation workers and packets never self-approve or merge; the operator or lead agent applies the standing reviewed-green merge rule above. - Command families, detailed CLI syntax, repository map, visual-proof flow, and Brain contribution:
AGENT_REFERENCE.md. Read only the section needed for the task.
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.

