Report · marked 25 Aug 2026
gitroomhq/postiz-app
Solid foundations, held back in a few specific places.
TypeScript · 35,125 stars · 943 files · branch main
72
/100
B+
Instructions
16/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on agent instruction file and instruction quality.Setup
20/20Whether an agent can install the project and get it running without a human. Full marks.Verification loop
16/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on tests exist and static type checking.Context economy
13/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability
8/10How quickly anything new can orient itself. Losing marks on written documentation.
Higher is better. Accent marks what is costing you most.
Fix these first
01
Tests exist
This is the single highest-leverage change on this page. Agents don't need full coverage, they need one command that goes red when they break something. Even a handful of tests on the core path converts blind editing into a feedback loop.
02
Instruction quality
Worth fixing: it never states a build, test, or run command; has no headings to structure it; has no code blocks.
03
File sizes fit in context
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
The full marking
Every deduction below names the file or setting it came from.
Instructions 16/27 B-
Whether the repo tells an agent how to behave before it starts guessing.
✗Agent instruction file
9/12
CLAUDE.md is present, but not the vendor-neutral AGENTS.md.
Rename or symlink to AGENTS.md so tools other than one vendor's can read it. Keeping CLAUDE.md alongside it costs nothing.
Also found: Copilot instructions
✗Instruction quality
4/12
Present but too thin to change an agent's behavior.
Worth fixing: it never states a build, test, or run command; has no headings to structure it; has no code blocks.
4,129 characters, a workable length
✓README as an entry point
3/3
README has a clear getting-started section.
Setup 20/20 A+
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
pnpm-lock.yaml pins the dependency tree.
Found pnpm-lock.yaml
✓Discoverable commands
6/6
Commands are declared where an agent will look for them.
package.json scripts (dev, dev-backend, pm2, publish-sdk, pm2-run, dev:stripe…)
✓Environment config
4/4
.env.example documents what the app needs to run.
✓Pinned runtime version
2/2
The language runtime version is pinned.
package.json engines.node >=22.12.0 <23.0.0
✓Reproducible environment
2/2
.devcontainer/devcontainer.json gives a known-good environment.
Verification loop 16/25 B
Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.
✗Tests exist
0/8
No test files found. An agent has no way to know whether its change broke anything.
This is the single highest-leverage change on this page. Agents don't need full coverage, they need one command that goes red when they break something. Even a handful of tests on the core path converts blind editing into a feedback loop.
✓Test command is discoverable
7/7
An agent can find and run `npm run test`.
✓Continuous integration
4/4
7 GitHub Actions workflows define what "passing" means.
✓Lint and format rules
3/3
eslint.config.mjs encodes the house style.
✗Static type checking
2/3
Type checking is configured, but not in strict mode.
Turn on `"strict": true`. Type errors are the fastest feedback an agent gets, and non-strict mode silently discards most of them.
Context economy 13/20 B
Whether the repo fits in a context window, or fights it.
✓No committed build output
6/6
No generated directories committed.
✓.gitignore hygiene
3/3
.gitignore covers 41 patterns.
✗File sizes fit in context
0/6
2 source files are over 100KB.
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
apps/frontend/public/f.js — 511KB
libraries/nestjs-libraries/src/integrations/social/hashnode.tags.ts — 115KB
✗Repository weight
4/5
About 50.6MB checked out, which is comfortable.
Here is your AGENTS.md
Drafted from what is actually in this repository: the install
command from your lockfile, the commands you already declare, your real directory layout. Anything
marked TODO needs a person. Save it at the root as AGENTS.md.
# AGENTS.md 📨 The ultimate agentic social media scheduling tool 🤖 ## Setup ``` pnpm install ``` ## Commands ``` pnpm dev # run locally pnpm build # produce a build pnpm test # run the test suite, must pass before any commit pnpm dev-backend pnpm pm2 pnpm publish-sdk pnpm pm2-run pnpm dev:stripe ``` ## Layout - `apps/` 419 source files - `libraries/` 308 source files - `var/` 3 source files ## Conventions - There are no tests yet. An agent has no way to check its own work here. - TypeScript is not in strict mode. Turning it on catches a whole class of mistakes before they run. - CI defines what passing means. See `.github/workflows/build-containers.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - `apps/frontend/public/f.js` is 511KB. It will not fit comfortably in context, so read it in parts. - Copy `.env.example` before running anything that needs configuration. --- Drafted by agentreadme.com from what is in this repository. Everything marked TODO needs a human. Check it in as AGENTS.md at the root.
Open the raw markdown
or
curl -o AGENTS.md agentreadme.com/draft/gitroomhq/postiz-app.md
Show the mark
The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.
[](https://agentreadme.com/gitroomhq/postiz-app)Other TypeScript repositories, marked
Think this mark is wrong?
Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.