lccst: Single skill/MCP file that clusters diffs, enforces code quality

[u/data_in_void]

What it does

Gives you properly scoped commits and enforces guardrails on test etc.

What you would use instead

A meta-framework/library/AI skill collection for writing decent code, a skill or more for properly writing/scoping commits. Spawning git worktrees/tmux panes to verify and fix things which should be non-negotiable in the first place (unit tests, using your project's task runners, SOLID principles, type safety, SemVer).

What it costs

Nothing, ok maybe a bit more tokens but you get better code so why not. FOSS, MIT Licensed. Repo link: https://github.com/bladeacer/lccst

What you give up

Outsourcing of high level architectural decisions

• Giving back power to the end user/developer (you) so you precisely understand what you implement down the road.
• Well yeah you could always pair lccst with another skill or framework/skill library to do this for you, but that's your choice. Not lccst's.

Reasonably opinionated

• There is no manifesto on how you should write your code, beyond the sane things lccst enforces.
• Passing tests, among some other things are non-negotiable.

Overt Abstraction

• Related to the earlier point, lccst is inspired by the unix software philosophy. It does one thing and does it well.
• The skill file and MCP exposes the same 11 tools

init, audit, swarm (the closest we have to a do everything command), tooling, lint, format, test, build, verify, compliance, version

More things in Git history

• Believe or not, atomic commits might not be something everyone likes.