adr
Architecture decision records: durable decisions with their date, context, and consequences — supersede, never rewrite.
What changed in the project's environment since you last synced: dependencies, migrations, new env keys.
> /plugin marketplace add azrtydxb/procoder > /plugin install procoder@procoder
How it fires
How this command gets triggered: by you, by Claude, or both.
/envContext preview
What this command does when you run it.
What changed in the project's environment since you last synced: dependencies, migrations, new env keys.
description: "What changed in the project's environment since you last synced: dependencies, migrations, new env keys."
The user invoked /procoder:env with arguments: $ARGUMENTS
The launcher is: "${CLAUDE_PLUGIN_ROOT}/hooks/launcher.sh"
After pulling, the repository can move under you: a lockfile changed, a migration landed, a new environment variable appeared. Nothing fails loudly — you just lose an afternoon to a bug that was a stale schema.
1. `launcher.sh env` — reports what changed since the last recorded sync: lockfile digests per ecosystem with the install command to run, migrations added or removed, and new keys declared in `.env.example` that your `.env` lacks. Key NAMES only; no value from either file is ever printed. 2. Act on what it says: install, migrate, add the variable. 3. `launcher.sh env --sync` — record the current tree as the new baseline. This is a statement that you HAVE installed and migrated, so run it after doing the work, never before. 4. Report-only by design: environment drift is judgment, never a block.
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.