btclib-org/ai-agents-process
The btclib-org process for coding agents: the btclib-iss, btclib-pr and btclib-table skills, the file they share, and the writer and reviewer agents
ARCHETYPE
Pragmatist
A balanced, no-drama setup: some rules, some tools, nothing extreme.
Copy this rig
# review before running: this installs third-party code
$ npx degit btclib-org/ai-agents-process/.claude ./rig-ai-agents-process # inspect, then merge into .claude/ MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.
$ npx degit btclib-org/ai-agents-process/skills/btclib-iss .claude/skills/btclib-iss $ npx degit btclib-org/ai-agents-process/skills/btclib-pr .claude/skills/btclib-pr $ npx degit btclib-org/ai-agents-process/skills/btclib-table .claude/skills/btclib-table
$ curl -fsSL --create-dirs -o .claude/agents/reviewer.md https://raw.githubusercontent.com/btclib-org/ai-agents-process/main/agents/reviewer.md $ curl -fsSL --create-dirs -o .claude/agents/writer.md https://raw.githubusercontent.com/btclib-org/ai-agents-process/main/agents/writer.md
This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:
{
"permissions": {
"deny": [
"Read(./.env)",
"Read(./.env.*)",
"Read(**/.env)",
"Read(~/.ssh/**)",
"Bash(git push --force:*)",
"Read(**/*.pem)",
"Read(.env)",
"Read(~/.aws/**)",
"Read(**/*.key)",
"Read(**/.env.*)",
"Bash(git push --force*)",
"Bash(rm -rf:*)",
"Bash(rm -rf *)",
"Bash(sudo *)",
"Bash(sudo:*)",
"Bash(rm -rf /)",
"Bash(git push -f:*)",
"Read(.env.*)",
"Bash(git reset --hard*)",
"Bash(rm -rf /*)"
],
"ask": [
"Bash(git push:*)",
"Bash(git push *)",
"Bash(gh pr merge *)",
"Bash(git commit:*)",
"Bash(rm *)",
"Bash(gh pr merge:*)",
"Bash(gh pr create *)",
"Bash(git reset --hard:*)",
"Bash(npm publish:*)",
"Bash(git rebase *)"
]
}
} Skills (3)
Subagents (2)
| reviewer model: opus | Reviews a branch — code or text — at fresh context, before it is offered or landed. Answers CLEARED <sha> or CHANGES REQUESTED. Does not write in the tree. |
| writer model: opus | Writes a change — code or text — on a branch of its own in a git worktree, up to the gates its process names and a clean tree. It does not open pull requests, land, or review itself. |
Slash commands (1)
/review
Similar rigs
btclib-org/claude-process
The btclib-org process for coding agents: the btclib-iss, btclib-pr and btclib-table skills, the file they share, and the writer and reviewer agents
Pragmatist 524 tok · · Q0
paureis/pau-skills
The Claude Code skills, hooks and scripts I use every day packaged as a plugin
Orchestrator 1.1k tok · · Q15
OMOCHInoHOSHI/dotfiles-claude
.claude
Minimalist 177 tok · · Q19
Clarittyai/agentic-app-seed
Self-hostable template for building AI workflow automations and agentic apps: FastAPI, React and Postgres, wired for Claude Code. Docker-ready.
Pragmatist 11.3k tok · · Q25