Skip to content
Back to search

procoder

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.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/azrtydxb--procoder/badge.svg)](/listings/azrtydxb--procoder)

HTML

<a href="/listings/azrtydxb--procoder"><img src="/api/listings/azrtydxb--procoder/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

/plugin marketplace add azrtydxb/procoder
/plugin install procoder
/procoder:init          # installs the tools this repository needs

That's Claude Code; Procoder also ships adapters for **every agent** — Cursor, Windsurf, Cline, Kilo Code, Roo, Kiro, Codex CLI, Copilot CLI, Gemini, OpenCode, and anything that reads `AGENTS.md`. See [Every agent](https://procoder.azrty.com/portability/).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 14 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "procoder",
  3. "owner": {
  4. "name": "Pascal Watteel"
  5. },
  6. "plugins": [
  7. {
  8. "name": "procoder",
  9. "source": "./",
  10. "description": "A harness that gives AI coders the tools and skills to work like a senior developer",
  11. "homepage": "https://procoder.azrty.com/"
  12. }
  13. ]
  14. }
README.md · README · 212 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <img src="docs/assets/banner.png" alt="Procoder — senior dev wisdom, automated" width="100%">
  3. </p>
  4. **Make your AI coder work like a senior developer.** One Go binary gives
  5. the agent a commit gate it cannot talk its way past, quality controllers
  6. that refuse to call unfinished work done, and a self-learning loop that
  7. turns every escaped bug into a permanently closed class. The agent stays
  8. in control — nothing ever touches your code behind its back.
  9. ![CI](https://github.com/azrtydxb/procoder/actions/workflows/ci.yml/badge.svg)
  10. ![Version](https://img.shields.io/badge/version-3.9.5-7C3AED)
  11. ![License](https://img.shields.io/badge/license-Apache--2.0-7C3AED)
  12. ![Agents](https://img.shields.io/badge/works%20with-20%2B%20agents-7C3AED)
  13. ## Quick start
  14. ```
  15. /plugin marketplace add azrtydxb/procoder
  16. /plugin install procoder
  17. /procoder:init # installs the tools this repository needs
  18. ```
  19. That's Claude Code; Procoder also ships adapters for **every agent** —
  20. Cursor, Windsurf, Cline, Kilo Code, Roo, Kiro, Codex CLI, Copilot CLI,
  21. Gemini, OpenCode, and anything that reads `AGENTS.md`. See
  22. [Every agent](https://procoder.azrty.com/portability/).
  23. ## Before / after
  24. Without Procoder, "done" is whatever the agent last said. With it, done
  25. has to survive the gate — this is a real run, verbatim, on a demo repo
  26. with an unformatted file, a conflict marker, and a staged junk file:
  27. ```
  28. $ procoder check
  29. unformatted main.go (run `procoder format "main.go"` for the result)
  30. BLOCKING notes.md:1 merge conflict marker left in the file
  31. BLOCKING notes.md:5 merge conflict marker left in the file
  32. BLOCKING .DS_Store junk file staged — caches and garbage never belong in a commit
  33. ...
  34. procoder gate: 0 clean, 2 unformatted, 0 unchecked, 1 out of scope, 8 hygiene finding(s) (3 blocking)
  35. ```
  36. The agent gets the findings and the fixed content in the same turn; the
  37. binary never edits a file itself. And a tool that failed is **never**
  38. reported as clean — "unchecked" counts as failing, said out loud.
  39. ## How it works
  40. ```
  41. agent writes code ──► hook fires ──► binary computes findings
  42. ▲ │
  43. └──── agent reviews and implements ◄─┘
  44. ```
  45. Two modes, one principle:
  46. - **Self-serve** — tools the agent runs itself: check, format, lint,
  47. scan, query the index, audit the tree.
  48. - **Forced** — hooks at fixed lifecycle points (every write, every
  49. session start) the agent cannot skip.
  50. - **P-CONTROL** — the binary computes and reports; the agent acts.
  51. Nothing modifies code, files, or state behind the agent's back. The one
  52. exception is `procoder prune --apply`, which removes superseded copies of
  53. the plugin from your cache — not repository content, and never without
  54. being asked twice.
  55. ## What's inside
  56. **The commit gate** (`procoder check`) — formatting across the popular
  57. languages (Go, Python, JS/TS/HTML/CSS, PHP, Rust, C/C++, Java, Kotlin,
  58. Swift, Ruby, Dart, C#, shell — one canonical formatter each, the
  59. project's config always wins), git hygiene (conflict markers, junk, oversized
  60. files, AI-attribution lines), secrets, lint, ci and infra hygiene, and
  61. documentation health, all through one code path so `check`, `git`, and
  62. CI can never disagree.
  63. That full set is what a repository that has **adopted** procoder gets — one
  64. with a `.procoder/` directory, or an `AGENTS.md` naming procoder. In
  65. somebody else's repository only the checks that are true anywhere run
  66. (secrets, oversized files, conflict markers, junk, AI-attribution lines),
  67. and the ones that read file content see only the lines your commit wrote.
  68. procoder does not apply its conventions to a project that never asked for
  69. them, and every run says which mode it was in.
  70. **The quality chain** — thinking before code, with a refusing controller
  71. at every link: a **spec** interview closes design gaps before anything is
  72. built (`spec check` blocks while sections are missing or questions
  73. open), a **plan** turns the spec into tasks an engineer with zero
  74. context could execute (`plan check` blocks placeholders), a **backlog**
  75. holds larger projects as milestones → epics → user stories seeded from
  76. specs and worked in scope-boxed **sprints** (one active sprint, explicit
  77. carry-over, closes that refuse), and a **todo** list tracks standalone
  78. work (`todo close` refuses until every acceptance criterion is checked,
  79. evidence is recorded, and the gate is clean — story closes carry the
  80. same rigor).
  81. **The self-learning loop** — a pre-PR self-review catches
  82. reviewer-class findings before a PR exists; anything that still escapes
  83. becomes a **lessons** ledger entry whose adaptation (a linter rule, a
  84. rubric line, a pinning test) must land before the work counts as done.
  85. Downstream bot reviewers are the fallback net, not the net — and what
  86. that net catches is not lost either: `procoder copilot-leak` collects
  87. GitHub Copilot's auto-review findings, strips every trace of your code
  88. from them, and — only after you say yes on a terminal — files them as
  89. issues and records them as unlearned until someone writes the
  90. adaptation that closes the class.
  91. **The test domain** — `procoder test` runs the repository's real suite
  92. with each ecosystem's canonical runner (go test, cargo test, the
  93. package.json test script, pytest, gradle/maven): PASS with counts, FAIL
  94. with the failing tests named, and **NOT run**, which is never the same
  95. as green. Coverage is reported where the runner
  96. measures it natively and never enforced. Set `[test] policy = "block"`
  97. and a green suite becomes part of "done" — the closes refuse while it is
  98. red or unverifiable.
  99. **The release controller** — `procoder release` is the last refusal
  100. before a tag: the version in sync across every file you list, the
  101. changelog entry present, the tree clean, the gate clean, the suite
  102. green. Every failure arrives in one list, and on success the `git tag`
  103. command is printed for you to run. Procoder tags nothing itself.
  104. **The ten domains** — security (gitleaks, semgrep, osv-scanner), best
  105. practices (**lint** with curated baselines), **maintain**ability
  106. (dead code, complexity, plus **deps** freshness per ecosystem),
  107. **performance** (**bench** against a saved baseline — Go only, said out
  108. loud), **documentation** (broken refs, drift, diagrams, badges, **adr**
  109. decision records, this very README's completeness), clean code
  110. (formatting), **test**ing, **ci** (pinned actions, timeouts), **infra**
  111. (Docker, Terraform, Kubernetes, Helm), and GitOps discipline.
  112. **The code index** — ctags + SCIP, the agent's fast map: find, refs,
  113. callers, impact, unused, entrypoints.
  114. **Senior habits, encoded** — engineering **principles** injected at
  115. session start (build ladder: reuse → stdlib → platform → minimum code;
  116. delegation: parallel subagents under a contract, watched and judged;
  117. ADHD/ASD-friendly formatting for complex answers — problem cards,
  118. decisions surfaced, noise filtered; all repo-overridable), deliberate
  119. corner-cuts marked and harvested as
  120. **debt** with revisit triggers, and an **audit** command that onboards
  121. any existing codebase with a triaged scorecard.
  122. ## Replaces the plugins you are already running
  123. Procoder absorbed three earlier tools, and running them alongside it
  124. means two sets of instructions competing for the same agent:
  125. - **[superpowers](https://github.com/anthropics/claude-plugins-official)** —
  126. plans for an engineer with zero context, spike/bounded/architectural
  127. classification, evidence before "done", systematic debugging, TDD with
  128. the mutation check. All of it here, with controllers that refuse where
  129. the originals advised.
  130. - **[ponytail](https://github.com/DietrichGebert/ponytail)** — the build
  131. ladder, the `debt:` marker convention, the five-tag over-engineering
  132. review, one instruction file serving every agent.
  133. - **[serena](https://github.com/oraios/serena)** — symbol-level
  134. navigation, cross-file rename, interface implementations, project
  135. memory. Now `procoder index` and `.procoder/`, with no MCP server to
  136. keep running. Serena's symbol-level **write** tools are deliberately
  137. not adopted: the binary computes the rename and hands you the diff.
  138. Full provenance map, including where the serena replacement stops:
  139. [Influences](https://procoder.azrty.com/influences/).
  140. ## Configuration
  141. Everything Procoder owns lives in `.procoder/` — plain files, made to be
  142. edited, and the repo's version always wins over the built-in default:
  143. `config.toml` (policies, thresholds), `PRINCIPLES.md`, the github
  144. templates, the docs/security rules, the review rubric, the lessons
  145. ledger. Full reference:
  146. [Configuration](https://procoder.azrty.com/configuration/).
  147. ## The docs
  148. The full story lives on the site, organised the way the
  149. [Divio documentation system](https://docs.divio.com/documentation-system/)
  150. splits it: the tutorial
  151. ([Getting started](https://procoder.azrty.com/getting-started/)),
  152. the how-to guides
  153. ([Ship a change](https://procoder.azrty.com/workflow/)),
  154. the reference
  155. ([every command](https://procoder.azrty.com/commands/)), and
  156. the explanation
  157. ([the quality chain](https://procoder.azrty.com/quality-chain/),
  158. [how it's built](https://procoder.azrty.com/architecture/)).
  159. ## What the reports mean
  160. A file that could not be checked is never called clean. A task without
  161. fresh verification evidence cannot close. This README is held to a
  162. completeness check — a feature family it stops mentioning blocks the
  163. gate. No benchmark numbers appear here because none have been run; any
  164. future number will carry its method alongside it.
  165. Where the rigor costs more than it returns, and where a check is narrower
  166. than its name, is written down rather than left to be discovered:
  167. [Honest limits](docs/honest-limits.md). What layer procoder occupies, and
  168. what it does not try to be: [Where procoder sits](docs/positioning.md).
  169. The external evidence behind each premise, and the premises that have none,
  170. are separated and labelled in [Research](docs/research.md).
  171. ## Implementation
  172. One Go binary, no runtime dependencies, cross-compiled per platform into
  173. `dist/` and committed with the plugin — no npm, no network at hook time,
  174. air-gapped included. `go test ./...` to develop; the design contract
  175. lives in the docs and supersedes anything here that drifts from it.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.