adr
Architecture decision records: durable decisions with their date, context, and consequences — supersede, never rewrite.
How to run this project: the launch commands it declares, with the file that declared each.
> /plugin marketplace add azrtydxb/procoder > /plugin install procoder@procoder
How it fires
How this command gets triggered: by you, by Claude, or both.
/runContext preview
What this command does when you run it.
How to run this project: the launch commands it declares, with the file that declared each.
description: "How to run this project: the launch commands it declares, with the file that declared each."
The user invoked /procoder:run with arguments: $ARGUMENTS
The launcher is: "${CLAUDE_PLUGIN_ROOT}/hooks/launcher.sh"
1. Run `launcher.sh run`. It prints the launch command(s) this repository declares — package.json scripts, Makefile targets, a Go main, a Cargo bin, manage.py, docker compose, a Procfile — each with the file that declared it, most specific first. 2. Run the command you chose in your OWN shell, not through procoder: a server is long-running, and backgrounding plus log capture belong to the tool that owns the process. `--exec` exists only for a single one-shot command and refuses when there is a choice to make or the command looks like a server. 3. No candidates is a real answer: a library has nothing to run. 4. Tests are a different question — use /procoder:test.
Senior-developer discipline for AI coding agents. A commit gate that counts unchecked as failing, quality controllers that refuse to call unfinished work done, and a lessons loop that closes each escaped bug's class. One Go binary, no runtime deps, works with 20+ agents.
Architecture decision records: durable decisions with their date, context, and consequences — supersede, never rewrite.
Onboard an existing codebase: every domain's checks over the whole tree, then a triaged plan to bring it in line.
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
Run the formatting gate over the changed files, as a commit or CI would.
CI/CD hygiene and run health: pinned actions, timeouts, concurrency, tests — plus the latest runs via gh.
Copilot's auto-review escapes: find them since the last look, sanitise them, and turn each one into a lesson.