dzhioevdzhioev/bro/oops/AGENTS.md

bro / oops

AGENTS.md12 starsChanged 13 days agoApache-2.0View on GitHub

oops/ is the bro-oops uv workspace member. It owns reusable deployment and operations machinery while account and service configuration stays with the consuming repository. The root repository owns formatting, lint, typing, packaging policy, and the test gate. - bro/oops/assets.py — validates and locates the shell assets shipped in the wheel - bro/oops/targets.py — typed deploy-target declarations and the per-repository registry loader - bro/oops/mcp.py — infra MCP operations over the repository's registered targets - bros/devoops/ — the operations persona and its…

Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bench/AGENTS.mdAGENTS.md
- benchmark/AGENTS.mdAGENTS.md
- bro/AGENTS.mdAGENTS.md
- browser/AGENTS.mdAGENTS.md
- dev/AGENTS.mdAGENTS.md
- filetypes/AGENTS.mdAGENTS.md
- local/AGENTS.mdAGENTS.md
- ride/AGENTS.mdAGENTS.md

The file

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

Very specific:
Run the image check on the host, through the docker gate stage.
line 22

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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

bro-oops

oops/ is the bro-oops uv workspace member. It owns reusable deployment and operations machinery while account and service configuration stays with the consuming repository. The root repository owns formatting, lint, typing, packaging policy, and the test gate.

Components

bro/oops/assets.py — validates and locates the shell assets shipped in the wheel
bro/oops/targets.py — typed deploy-target declarations and the per-repository registry loader
bro/oops/mcp.py — infra MCP operations over the repository's registered targets
bros/devoops/ — the operations persona and its target-driven deploy spell
bro/oops/config.py — resolves the infra credential into typed deployment configuration and neutral defaults
bro/oops/wheel_staging.py — resolves an image's framework declaration to the workspace distributions it stages
bro/oops/infra/deploy_lib.sh — sourceable image-build, ECR, CodeBuild, wheel-staging, and CDK helpers
bro/oops/infra/monitor_ecs.sh — ECS deployment-state monitor
bro/oops/infra/buildspec.yml — consumer-configured CodeBuild image-build pattern
bro/oops/infra/server_base/ — local-only base image for Python services
trails/server/ — trails image, self-contained credential store with typed SSM annotations under creds.json sources, deployment, plan, bootstrap, local-run, and verification scripts entries.json declares the formats and wire decode sides served by the image; staging builds their providers from this workspace, or from the framework revision in a consumer's lock. The image checks every entry before listening, and verify_image.sh exercises recording and projection from image_cases.json, plus startup with a declared distribution removed. Run the image check on the host, through the docker gate stage.
image_build.sh — the trails target used by the shared CodeBuild buildspec
deploy_targets.py — this repository's trails-server operations declaration
cdk/ — the bro-oops-cdk project: the CDK stacks and this repository's CDK app, in an environment of their own (cdk/AGENTS.md)

Nothing this member ships imports the CDK, and it declares no CDK dependency: the persona, the toolset, and the configuration run in every session's runtime, which must not carry it.

Build the member with uv build --package bro-oops. Regenerate its console scripts and committed bridge with sync-scripts --project oops.

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