agentleFS
Sign inStart free
ayudayayuday/gstack/AGENTS.md

gstack

AGENTS.md0 starsChanged 7 months agoMITView on GitHub

gstack is a collection of SKILL.md files that give AI agents structured roles for software development. Each skill is a specialist: CEO reviewer, eng manager, designer, QA lead, release engineer, debugger, and more. Skills live in .agents/skills/. Invoke them by name (e.g., /office-hours).

  • Deletes or force-pushes

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run bun run gen:skill-docs --host codex to regenerate Codex-specific output.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

gstack — AI Engineering Workflow

gstack is a collection of SKILL.md files that give AI agents structured roles for software development. Each skill is a specialist: CEO reviewer, eng manager, designer, QA lead, release engineer, debugger, and more.

Available skills

Skills live in .agents/skills/. Invoke them by name (e.g., /office-hours).

SkillWhat it does
/office-hoursStart here. Reframes your product idea before you write code.
/plan-ceo-reviewCEO-level review: find the 10-star product in the request.
/plan-eng-reviewLock architecture, data flow, edge cases, and tests.
/plan-design-reviewRate each design dimension 0-10, explain what a 10 looks like.
/design-consultationBuild a complete design system from scratch.
/reviewPre-landing PR review. Finds bugs that pass CI but break in prod.
/debugSystematic root-cause debugging. No fixes without investigation.
/design-reviewDesign audit + fix loop with atomic commits.
/qaOpen a real browser, find bugs, fix them, re-verify.
/qa-onlySame as /qa but report only — no code changes.
/shipRun tests, review, push, open PR. One command.
/document-releaseUpdate all docs to match what you just shipped.
/retroWeekly retro with per-person breakdowns and shipping streaks.
/browseHeadless browser — real Chromium, real clicks, ~100ms/command.
/setup-browser-cookiesImport cookies from your real browser for authenticated testing.
/carefulWarn before destructive commands (rm -rf, DROP TABLE, force-push).
/freezeLock edits to one directory. Hard block, not just a warning.
/guardActivate both careful + freeze at once.
/unfreezeRemove directory edit restrictions.
/gstack-upgradeUpdate gstack to the latest version.

Build commands

bun install              # install dependencies
bun test                 # run tests (free, <5s)
bun run build            # generate docs + compile binaries
bun run gen:skill-docs   # regenerate SKILL.md files from templates
bun run skill:check      # health dashboard for all skills

Key conventions

  • SKILL.md files are generated from .tmpl templates. Edit the template, not the output.
  • Run bun run gen:skill-docs --host codex to regenerate Codex-specific output.
  • The browse binary provides headless browser access. Use $B <command> in skills.
  • Safety skills (careful, freeze, guard) use inline advisory prose — always confirm before destructive operations.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free