ESLint checks your code. Prettier formats it. But nothing checks your repo structure.
I kept reviewing AI-agent creations where the code compiled and was tested, documentation may have been there - but it was a MESS. Files were in the wrong folder, naming conventions were broken, random markdowns, scripts, and files were laying about like kid who never cleans their room.
So I built Repotype.
npx repotype validate .
It validates folder structure, file naming (kebab-case enforcement), documentation frontmatter, and content policies (secret detection, forbidden patterns). Config is a simple YAML file. There's also an autofix command for some issues.
Given how 'simple' it is, I'm very impressed. With it, we built www.clawx.ai over the weekend, helped fix/repair other projects like interface.supernal.ai (used in testing), launched www.computationrights.org. All while I was doing family things.
It certainly is not perfect. Not completely autonomous. It is much faster than Claude or Cursor.
It's already getting better. We're re-architecting its memory, pulling in research, notes from open source, trial-error it ourselves too.
backlog.md has been nice to help with organization but it is not sufficient for complexity or multiagents etc.
I kept reviewing AI-agent creations where the code compiled and was tested, documentation may have been there - but it was a MESS. Files were in the wrong folder, naming conventions were broken, random markdowns, scripts, and files were laying about like kid who never cleans their room.
So I built Repotype.
It validates folder structure, file naming (kebab-case enforcement), documentation frontmatter, and content policies (secret detection, forbidden patterns). Config is a simple YAML file. There's also an autofix command for some issues.
MIT licensed.
GitHub: https://github.com/supernalintelligence/repotype npm: https://www.npmjs.com/package/repotype Docs: https://supernalintelligence.github.io/repotype/