Repository navigation
Stacks
Milimarty edited this page Oct 19, 2026
·
1 revision
Build › Stacks shows how each project builds and tests. A stack is one YAML file: its lane (api or web), the files that show a project uses it, its test layers, its commands (test one criterion, every test, coverage, static checks, migrate, compile) and its tools (formatters, linters, pre-commit).
-
New stack asks step by step: lane, the files that detect it, test layers, commands, tools. keel reads your
project first (package.json scripts, Gradle, Maven, pyproject, composer.json, go.mod, a Makefile, pre-commit) and
fills each step; you change what you like. Then keel checks it (nothing is saved yet) and Save the stack writes
.keel/stacks/<name>.yml. -
Remove takes away a stack the project added (its own, an installed pack, one from the marketplace), after a yes.
keel's own stacks cannot be removed (other projects use them): Turn off for this project stops keel using one
here (
stacks: {ignore: [...]}in.keel/config.yml); Turn on brings it back. - Find stacks opens Marketplace › Stacks.
- Test filters:
{AC}is the criterion id (AC-006),{AC_ID}the same without the dash (AC006) for Java class names. Maven-Dtestand Gradle--testsfilters written with{AC}also matchAC006….
The same from keel TUI (/stacks, /stack <name>, /stack remove <name>, /stack off <name>, /stack install <name>, /create stack) and MCP (keel_stacks, keel_stack, keel_stack_suggest, keel_stack_check,
keel_stack_create, keel_stack_remove, keel_stack_off, keel_stack_market_install). Ask KeelBot "write a stack
for this project": it gives a Save the stack card, checked by keel first.
From docs/GUIDE.md · All pages
keel v2
- Home
- How a flow works
- Flows in detail
- Web research
- Rules
- KeelBot
- keel TUI (keel2 tui)
- Thinking effort
- Plugins and the Marketplace
- Stacks
- Plugins: Database, Git and CI/CD
- Quality
- Inbox and run modes
- Usage and caps
- Tasks and Jira
- Logins
- Signing in
- Use keel from Claude Code or Claude Desktop (MCP)
- keel2 commands
- Where keel keeps its files (layouts)
- Native mode (no Docker)
- Docker mode
- Several project folders
- Git worktree projects
- Problems
- Folders in the container
- Without the install script
- Develop keel v2