CodeStable plugin
A plugin of eight skills for Claude Code and Codex that keeps work in a long-lived project bounded, verified by evidence and remembered
- 1,112 ★ on the repository
- Last commit
Extended access
Why this level
- The skills write code and tests in the repository, and cs-onboard and cs-keep create files in the .codestable folder
- Bug fixes and refactoring run tests and change existing code
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/codestableDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The skills write code and tests in the repository, and cs-onboard and cs-keep create files in the .codestable folder
- Bug fixes and refactoring run tests and change existing code
This is third-party code. Review the repository files before installing.
What it does
CodeStable is a plugin of eight skills for development in projects that live for months and years. The entry skill cs works out what the user wants: do the task right away, discuss it or give advice. The others own their kinds of work. cs-feat adds features, cs-issue finds the cause of a bug and, once allowed, fixes it with a red-then-green test, cs-refactor changes structure while checks confirm behavior, cs-epic splits a large task into subtasks. The cs-review skill is read-only: it makes one review pass and creates no subagents. cs-keep maintains verified project facts and lessons. cs-onboard creates a minimal .codestable folder in the repository with an attention.md file holding up to 25 facts needed in every session, plus the lessons and work folders. The authors name three principles: a thin harness with thick context, evidence before conclusions and one owner for each fact. For an ordinary task CodeStable creates no intermediate documents; the diff, test output and delivery note serve as evidence. A person steps in when product requirements change, on serious risks and at final acceptance.
Who it is for. Developers and teams that run one product for years with Claude Code or Codex and want the agent to remember constraints and prove its results.
Good fit when
- The project is years old and different agent sessions confuse earlier agreements
- A bug has to be fixed with proof: first a failing test, then the fix and a green run
- A refactoring must not change behavior, and before the edit you need evidence that behavior will hold
- A large task has to be split into subtasks and followed against an approved plan
- Findings from earlier sessions should become lessons that later agents pick up
Not a fit when
- You want a throwaway prototype nobody will maintain: the overhead of project memory does not pay off
- You need team-of-agents orchestration with automatic handoff: CodeStable does not do it, and the authors recommend the separate cs-agent
- The project already runs its own documentation system and a second one is unwanted: the plugin does not replace ADRs and issues
- You want one pipeline for every task without exception: CodeStable adds checks where they are needed
Example request
/cs-issue The checkout test fails only in CI. Find the cause, show the red test first and apply the fix after I confirmLimitations
The README labels the project beta. The main description is in Chinese, with an English version in README.en.md. The MIT license is named in the README, but GitHub did not detect it. Users of version 1 must remove 24 retired entry points following UPGRADE.md before installing version 2. If the marketplace catalog does not find the plugin, the --full-depth flag helps. The last commit is from August 2026. The author does not describe a separate install for Cursor.
How to disable. In Claude Code run /plugin uninstall codestable@codestable. If installed through npx skills, delete the cs skills from .claude/skills or .agents/skills. Delete the .codestable folder in the project by hand if the project memory is no longer needed.
FAQ
How do I install CodeStable in Claude Code?
Run /plugin marketplace add codestable/CodeStable, then /plugin install codestable@codestable. For Codex the commands are codex plugin marketplace add codestable/CodeStable and codex plugin add codestable@codestable. The CLI route is npx skills@latest add codestable/CodeStable/plugins/codestable.
What does /cs-onboard do?
It creates a minimal .codestable folder in the repository with an attention.md file and the lessons and work directories. The skill leaves project documents, branch layout and worktrees alone.
Which skill do I call when unsure?
Call /cs. It decides whether to do the task right away, discuss it in the session or give advice, and hands the work to cs-feat, cs-issue, cs-refactor or cs-epic when needed.
How much project information does attention.md hold?
At most 25 facts needed in every session. Other findings go to lessons, one file per lesson, and move through the observed, validated and retired stages.
Does CodeStable replace an agent orchestrator?
No. The plugin covers boundaries, evidence and memory and does not assemble agent teams. For several agents working together the authors recommend the separate cs-agent project.
Discussion
No questions or reviews yet.
Related
PluginsA plugin that readies a project for Claude Code: guidance, tests, review, TDD, refactoring and a resumable fix loop
Eleven skills for Claude Code and Codex: test audit, git worktree cleanup, plan pages, screen recording transcripts and 1Password sign-in
A 33-skill plugin with gates: question the request, verify facts against sources, test first, review by a second model
The ce plugin for Claude Code and Codex: eleven skills and four sub-agents for plans, review, tests, architecture and writing.
A Claude Code and Codex plugin with skills for code research, tests, refactoring and independent review of finished changes
A 13-skill delivery workflow for coding agents: from idea to plan, review, security audit, tests and a shipped pull request
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| CodeStable (this card) | no | 1,112 | |
| Superpowers | no | 316,679 | sets one process of plan, TDD and subagents, while CodeStable adds checks where needed and project memory in .codestable |
| Spec Kit | no | 149,633 | drives development from a spec through the specify CLI, while CodeStable scales verification to the risk of the task |
README in short
The description opens with a flow chart: a user request passes through cs, then through feat, issue, refactor or epic to verification and review. Three install routes follow, then a table of eight skills, the principles and how project memory is laid out. It ends with a two-layer model for large tasks, the limits of applicability and a list of documents for deeper reading.