A lean, agent-friendly zsh theme repository with clear guidelines and test infrastructure, missing only strict environment locking.

19 of 42 checks passed across 6 categories.

• Machine Orientation

  ✓6 checks passed⚠4 problems found

  • lowllms.txt present

    An llms.txt is the emerging machine-orientation standard — a curated map for LLMs.

    Fix: Add an llms.txt pointing at the key docs and entry points.

  • lowArchitecture doc

    An ARCHITECTURE doc hands an agent the module map instead of making it infer one.

    Fix: Add an ARCHITECTURE.md describing the major components and how they fit.

  • lowREADME shows usage

    A usage/example section tells an agent how the project is actually invoked.

    Fix: Add a Usage or Examples section to the README with a runnable snippet.

  • lowExamples directory

    An examples/ directory gives an agent runnable, copyable references for the API.

    Fix: Add an examples/ directory with small, runnable usage samples.

  • ✓README present — An agent reconstructs what the repo is and how to work in it from the README first.
  • ✓Agent instructions file — AGENTS.md / CLAUDE.md is the direct, machine-read channel for entry points and conventions.
  • ✓Agent instructions stay lean — A bloated instructions file burns context and measurably hurts more than it helps.
  • ✓Repository description set — The one-line description is the fastest orientation signal an agent reads.
  • ✓Topics set — GitHub topics situate the repo's domain and stack for an agent at a glance.
  • ✓Contribution conventions are written down — A contributor guide is where an agent learns the branch, commit, and review conventions it must follow.

• Reproducible Setup

  ✓1 check passed⚠5 problems found

  • highLockfile committed

    Without a lockfile two clones can resolve different dependency trees — the build isn't reproducible.

    Fix: Commit your lockfile (package-lock.json / pnpm-lock.yaml / Cargo.lock / …).

  • mediumRuntime / toolchain pinned

    An unpinned runtime makes an agent guess the version a clean environment needs.

    Fix: Pin the runtime with .nvmrc / .tool-versions / an engines field / packageManager.

  • mediumContainer or dev-container

    A Dockerfile / compose / devcontainer removes 'works on my machine' from setup.

    Fix: Add a Dockerfile, a compose file, or a .devcontainer so the environment is declared, not assumed.

  • lowEnv template present

    A .env.example tells an agent which configuration keys it must supply to run.

    Fix: Ship a .env.example listing every required key with placeholder values.

  • lowDev container

    A .devcontainer gives an agent a one-command, fully-declared environment.

    Fix: Add a .devcontainer so the toolchain is declared, not assumed.

  • ✓README documents setup — Explicit install/setup steps are what let an agent go from clone to running.

• Code Navigability

  ✓2 checks passed⚠2 problems found

  • lowFormatter configured

    A formatter config (Prettier/Biome/rustfmt/…) keeps style uniform across the tree.

    Fix: Add a formatter (Prettier, Biome, rustfmt, …) and commit its config.

  • lowTyped public API

    A declared `types` entry gives an agent typed signatures to anchor an edit on.

    Fix: Ship type declarations and point package.json `types`/`typings` at them.

  • ✓Conventional source layout — A recognised src/ · lib/ · app/ layout lets an agent localise code without spelunking.
  • ✓.editorconfig present — An .editorconfig keeps whitespace and encoding consistent, so diffs stay legible.

• Verification Surface

  ✓1 check passed⚠6 problems found

  • highTests present

    Runnable tests are the ground truth an agent checks its own edits against.

    Fix: Add a test suite an agent can run to verify a change.

  • mediumTest command defined

    A `test` script is the documented, discoverable way to run the suite.

    Fix: Add a `test` script (package.json / Makefile / Taskfile) that runs the suite.

  • lowLint command defined

    A linter an agent can run catches a class of mistakes before they ship.

    Fix: Add a `lint` script and a linter config.

  • lowTask runner present

    A Makefile / Taskfile / justfile gives an agent a single index of the project's commands.

    Fix: Add a Makefile / Taskfile / justfile collecting the common commands.

  • lowTypecheck command

    A typecheck script lets an agent catch type errors before they ship.

    Fix: Add a `typecheck` script (e.g. `tsc --noEmit`).

  • lowBuild command

    A documented build command is the discoverable way for an agent to produce artifacts.

    Fix: Add a `build` script that produces the distributable.

  • ✓CI configured — Readable CI is the feedback loop an agent reads to know what 'green' means here.

• Agent Safety

  ✓7 checks passed⚠4 problems found

  • medium.gitignore covers env files

    An ignore rule for .env is what keeps the next careless commit from leaking secrets.

    Fix: Add `.env` (and `.env.*`) to .gitignore.

  • mediumPolicy names the threat model

    A scanning agent aims at what the repo says it is defending, and where untrusted input crosses in.

    Fix: Describe the threat model and trust boundaries in SECURITY.md — what is attacker-controlled, and where it reaches trusted code.

  • mediumPolicy scopes what counts as a finding

    With no reportable-finding bar and no out-of-scope list, an automated scan returns noise nobody triages.

    Fix: State in SECURITY.md what counts as a reportable finding, and what is out of scope or accepted risk.

  • lowPolicy gives severity context

    Severity judged against this system beats a generic rating an agent had to guess at.

    Fix: Say in SECURITY.md how severity is judged here — what makes a finding critical for this system.

  • ✓No committed .env — A tracked real .env hands secrets to anything — including an agent — that reads the repo.
  • ✓No exposed secrets — Secret-shaped literals in tracked files are a live credential leak.
  • ✓CODEOWNERS present — CODEOWNERS marks the 'don't touch without review' zones an agent should respect.
  • ✓Automated dependency updates — Dependabot / Renovate keeps dependencies patched without a human in the loop.
  • ✓.gitignore present — A .gitignore is the first guard against an agent committing secrets or build junk.
  • ✓Security policy — A SECURITY.md is where an autonomous security agent reads this repo's rules before acting on it.
  • ✓License makes the code reusable — Without a license an agent cannot safely copy, redistribute, or vendor any of this code.

• Context Economy

  ✓2 checks passed⚠2 problems found

  • lowGenerated / vendored files marked

    A .gitattributes linguist marker tells tools (and agents) what to skip.

    Fix: Mark generated/vendored paths in .gitattributes (linguist-generated / linguist-vendored).

  • lowNo oversized source file

    A single file in the hundreds of KB blows past an agent's effective context window.

    Fix: Split the largest files along their natural seams.

  • ✓Dependencies not vendored in — A committed node_modules / vendor tree drowns the real signal an agent needs.
  • ✓Build output not committed — Generated dist/ · build/ output is noise an agent has to read past.

14 of 32 checks passed across 6 categories.

• First Impression

  ✓3 checks passed⚠3 problems found

  • mediumREADME shows what it does

    A usage/example section lets a newcomer see the tool in action before committing.

    Fix: Add a Usage or Examples section with a concrete, copy-pasteable example.

  • lowStatus badges

    Build/version badges signal at a glance that the project is alive and healthy.

    Fix: Add a few status badges (CI, version, license) near the top of the README.

  • lowExamples to learn from

    An examples/ directory gives a newcomer something concrete to run and adapt.

    Fix: Add an examples/ directory with small, runnable samples.

  • ✓README present — The README is the first screen — with none, a newcomer has nothing to land on.
  • ✓Repository description set — The one-line description sets expectations before a newcomer even opens the README.
  • ✓Topics set — Topics situate the project's domain at a glance and help a newcomer find it.

• Getting Running

  ✓1 check passed⚠5 problems found

  • highLockfile committed

    Without a lockfile a newcomer's install resolves differently and hits errors the docs don't mention.

    Fix: Commit your lockfile so a fresh clone installs the same dependency tree.

  • mediumPrerequisite versions pinned

    Unpinned prerequisites are the classic 'works on my machine' first-run failure.

    Fix: Pin the required versions with .nvmrc / .tool-versions / an engines field.

  • mediumOne-command environment

    A Dockerfile / compose / devcontainer turns a fiddly setup into one command.

    Fix: Add a Dockerfile, a compose file, or a .devcontainer for a one-command setup.

  • lowEnv template present

    A .env.example shows a newcomer exactly which settings they must fill in to run it.

    Fix: Ship a .env.example listing every required key with placeholder values.

  • lowOne-click dev container

    A .devcontainer lets a newcomer start in a cloud IDE with zero local setup.

    Fix: Add a .devcontainer for a one-click, batteries-included environment.

  • ✓README documents setup — Explicit install steps are the difference between a 5-minute start and giving up.

• Finding Your Way

  ✓2 checks passed⚠3 problems found

  • mediumArchitecture / overview doc

    An overview hands a newcomer the map instead of making them reconstruct it.

    Fix: Add an ARCHITECTURE.md (or a 'Project layout' README section) naming the key directories.

  • lowNo oversized source file

    A single thousand-line file is a wall a newcomer bounces off.

    Fix: Split the largest files along their natural seams.

  • lowFormatter configured

    An auto-formatter means a newcomer never guesses the house style.

    Fix: Add a formatter (Prettier, Biome, rustfmt, …) and commit its config.

  • ✓Conventional source layout — A familiar src/ · lib/ · app/ layout lets a newcomer guess where things live.
  • ✓.editorconfig present — Consistent indentation/encoding keeps the code readable and diffs clean for newcomers.

• Path to Contribute

  ✓3 checks passed⚠3 problems found

  • lowTest command defined

    A documented test command lets a contributor check their change before opening a PR.

    Fix: Add a `test` script that runs the suite.

  • lowLint command

    A linter lets a first-time contributor catch style issues before review.

    Fix: Add a `lint` script and a linter config.

  • lowTask runner

    A Makefile / Taskfile gives a contributor a single index of the project's commands.

    Fix: Add a Makefile / Taskfile collecting the common dev commands.

  • ✓CONTRIBUTING guide — A CONTRIBUTING guide is the difference between a guessed and a guided first PR.
  • ✓Issue templates — Issue templates show a newcomer how to file something useful — and that contributions are welcome.
  • ✓Pull-request template — A PR template tells a first-time contributor what a good change includes.

• Signs of Life

  ✓2 checks passed⚠3 problems found

  • mediumTests present

    A test suite signals a project that's cared for, not abandoned.

    Fix: Add a test suite — it's the clearest sign the project is maintained.

  • lowChangelog

    A maintained CHANGELOG shows a newcomer the project ships and records its changes.

    Fix: Keep a CHANGELOG.md (e.g. the Keep a Changelog format).

  • lowFunding configured

    A FUNDING config signals an invested, sponsored project — not a one-off dump.

    Fix: Add a .github/FUNDING.yml if the project accepts sponsorship.

  • ✓CI configured — Green CI on every change tells a newcomer the project is actively kept working.
  • ✓Automated dependency updates — Dependabot / Renovate activity is a visible heartbeat of ongoing maintenance.

• Open Door

  ✓3 checks passed⚠1 problem found

  • lowCode of conduct

    A code of conduct states the social ground rules that make it safe to step in.

    Fix: Add a CODE_OF_CONDUCT.md (the Contributor Covenant is the de-facto standard).

  • ✓License present — With no license the project isn't legally reusable — the door is shut however friendly the README.
  • ✓License is a standard one — A non-standard or custom license is a legal question mark a newcomer won't resolve.
  • ✓Security policy — A SECURITY.md tells a newcomer how to report a problem responsibly.