Stack

Adams forPython projects.

A script that works today becomes a service tomorrow. Adams keeps keys out and the growth on plan.

Lite and Pro
// the problem

What goes wrong

Keys live in scriptsA quick script has its key at the top. Months later that script is in a shared repo.
Growth without a planFunctions pile into one file. Nobody agreed on the structure, so every change touches everything.
// what adams does

What Adams does

Catches keys in scriptsLite: a key assigned in a .py file is stopped at commit and moved to an env variable.
Asks about structure firstPro: before a script becomes a package, a few questions settle layout and limits.
Reviews separatelyPro: a reviewer ranks problems such as unchecked input and broad exception handling.
// worked example

An example

A key at the top of a script

Illustrative output.

~/project~/your-project · example
$ git commit -m "add sync script"
adams: blocked
An API key in sync.py:3
Now read from the environment
✓ Committed, no secrets found
// faq

Questions

Does it run my tests?

It can run the checks your project already has, when you ask.

Does it need a special setup?

No. It works on the files your AI writes.

What is free?

The secret and git guards.

// related

Keep reading