F
felipe-diniz/keel
Claude Code plugin: explore, implement, test, research and review agents, a single pre-commit gate for…
★ 4·updated 2026-11-16
View on GitHub ↗Link checked 2026-11-17 · HTTP 200 · opens the vendor's own site
- Star count
- 4 ★ · felipe-diniz/keel · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-16 · last seen 2026-11-20 · seen 5× · listed by 2 sources
- Score
- score 203 · 4 ★ · 2 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Agent skills. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
felipe-diniz/keel;first catalogued 2026-11-16;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# keel
Excerpted from the repository README (abridged)
A Claude Code plugin that ships a ready-made working method: five agents, a single pre-commit review gate, a skill for running several fronts in parallel as background sessions, web skills (public sites, product screens, the modern web platform, SEO), an LGPD skill that teaches the law and hunts personal-data leaks in code, and per-developer versioned project memory. The main session thinks and decides. Wide reading, isolated writing and web research run outside it, in separate contexts.
Install it and start working. There is no setup step.
## Why use it
Quality where it matters
There is one review gate, keel:critical-review, before the commit. It runs only when the session changed a critical-risk invariant (money, auth, tenant isolation and the like).
It runs once, at the end, with tests green, at max effort. It reviews the critical hunks and their siblings (callers, consumers, the tests on that path).
Changes with no critical risk ship with tests and lint. Docs, i18n and the rest pay no review tax.
The implement agent does not touch critical domains. That work stays in the main session.
Lower cost and faster sessions
Wide reading goes to keel:explore (haiku, read-only), which returns only a synthesis with file:line references. Isolated writing goes to keel:implement (sonnet), and tests to keel:test (sonnet), reviewed by the main session. Web research goes to keel:research (sonnet). The main context stays small, so each turn is cheaper and compaction comes later.
The lean profile used for background sessions cut the per-call base from 72k to 40k tokens. The skill listing in background sessions went from 22,662 to 4,779 characters.
Each rule lives in one place, and a skill keeps a short core with the detail in references read on demand. In 3.4.0 the coordinator's core went from 23,395 to 19,693 bytes, under the 20,000 characters that come back after compaction, and what every session carries stayed at about 13.8 KB with a new skill on board. Test-pinned caps keep it there (CHANGELOG).
The 400k compaction window cost the same as 300k in measurement and compacts less often. Each compaction loses detail.
The rules say what compaction must preserve: the request in the user's own words, literal approvals, files, commands with their results, and the gate state.
Long autonomous runs
Parallel fronts run as real background sessions (claude --bg) for 12 to 20 hours, one session per front, with a queue, a resource window and a commit mode.
Questions from every front are asked up front, before the run starts.
With nobody there to type /clear, a relay replaces it: the coordinator opens its successor, checks that it is alive and exits.
Shared, versioned memory per developer
Each developer writes to their own folder in .claude/memory/, so merges never conflict on the index. The team still reads each other's lessons, and git gives history and review. Details in Versioned memory.
Guardrails enforced by hooks, not by hope
The gate hook refuses a call without a briefing, and asks for confirmation from the second pass in a session.
Inside the reviewer, a Bash guard blocks anything that changes state: git that mutates the tree, writes outside the temp directory, full test suites, builds, servers, migrations, package installs and external network.
Install it and start working. There is no setup step.
## Why use it
Quality where it matters
There is one review gate, keel:critical-review, before the commit. It runs only when the session changed a critical-risk invariant (money, auth, tenant isolation and the like).
It runs once, at the end, with tests green, at max effort. It reviews the critical hunks and their siblings (callers, consumers, the tests on that path).
Changes with no critical risk ship with tests and lint. Docs, i18n and the rest pay no review tax.
The implement agent does not touch critical domains. That work stays in the main session.
Lower cost and faster sessions
Wide reading goes to keel:explore (haiku, read-only), which returns only a synthesis with file:line references. Isolated writing goes to keel:implement (sonnet), and tests to keel:test (sonnet), reviewed by the main session. Web research goes to keel:research (sonnet). The main context stays small, so each turn is cheaper and compaction comes later.
The lean profile used for background sessions cut the per-call base from 72k to 40k tokens. The skill listing in background sessions went from 22,662 to 4,779 characters.
Each rule lives in one place, and a skill keeps a short core with the detail in references read on demand. In 3.4.0 the coordinator's core went from 23,395 to 19,693 bytes, under the 20,000 characters that come back after compaction, and what every session carries stayed at about 13.8 KB with a new skill on board. Test-pinned caps keep it there (CHANGELOG).
The 400k compaction window cost the same as 300k in measurement and compacts less often. Each compaction loses detail.
The rules say what compaction must preserve: the request in the user's own words, literal approvals, files, commands with their results, and the gate state.
Long autonomous runs
Parallel fronts run as real background sessions (claude --bg) for 12 to 20 hours, one session per front, with a queue, a resource window and a commit mode.
Questions from every front are asked up front, before the run starts.
With nobody there to type /clear, a relay replaces it: the coordinator opens its successor, checks that it is alive and exits.
Shared, versioned memory per developer
Each developer writes to their own folder in .claude/memory/, so merges never conflict on the index. The team still reads each other's lessons, and git gives history and review. Details in Versioned memory.
Guardrails enforced by hooks, not by hope
The gate hook refuses a call without a briefing, and asks for confirmation from the second pass in a session.
Inside the reviewer, a Bash guard blocks anything that changes state: git that mutates the tree, writes outside the temp directory, full test suites, builds, servers, migrations, package installs and external network.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/felipe-diniz-keel/)
- Source
- github · https://github.com/felipe-diniz/keel
- Browse by field
- Agent skills
- Traction
- 4 ★
- Listed by
- 2 independent sources
- added
- today
More entries
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.