omarshahineomarshahine/restaurant-cli/AGENTS.md

restaurant-cli

AGENTS.md11 starsChanged 11 days agoMITView on GitHub

This repo uses Clawpatch for local automated code review. Keep .clawpatch/ ignored; it is generated runtime state containing features, findings, reports, runs, and patch attempts. Standard workflow: If this repo needs hand-authored feature coverage, keep those curated definitions in tools/clawpatch/features/ and sync/copy them into .clawpatch/features/ before review. Do not commit .clawpatch/ generated state. Durable memory promoted from ~/.claude/projects/-Users-omarshahine-GitHub-restaurant-cli/memory during the AGENTS.md migration. Keep this section current when project-specific operating knowledge changes. Why: Stated preference while porting features from the table-reservation-goat…

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,774 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 repository2 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- restaurantSkill

The file

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

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
If this repo needs hand-authored feature coverage, keep those curated definitions in tools/clawpatch/features/ and sync/copy them into …
line 18
Very specific:
Do not use the word "goat" anywhere in restaurant-cli command names, flag names, subcommand names, or user-facing copy.
line 38

≈ “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

Clawpatch Code Review

This repo uses Clawpatch for local automated code review. Keep .clawpatch/ ignored; it is generated runtime state containing features, findings, reports, runs, and patch attempts.

Standard workflow:

clawpatch doctor
clawpatch init          # first time only
clawpatch map
clawpatch review --limit 10
clawpatch report --output .clawpatch/reports/summary.md
clawpatch show --finding <id>
clawpatch fix --finding <id>
clawpatch revalidate --finding <id>

If this repo needs hand-authored feature coverage, keep those curated definitions in tools/clawpatch/features/ and sync/copy them into .clawpatch/features/ before review. Do not commit .clawpatch/ generated state.

Imported Claude Project Memory

Durable memory promoted from ~/.claude/projects/-Users-omarshahine-GitHub-restaurant-cli/memory during the AGENTS.md migration. Keep this section current when project-specific operating knowledge changes.

memory/MEMORY.md

No "goat" in command/feature names — never use the word "goat" in command names, flags, or user-facing copy when porting from table-reservation-goat

memory/feedback_no_goat_naming.md

name: No "goat" in command/feature names description: Never use the word "goat" in restaurant-cli command names, flags, or user-facing copy when porting from table-reservation-goat type: feedback originSessionId: 9bf75f31-0ab9-4a07-bd45-3048d6703916

Do not use the word "goat" anywhere in restaurant-cli command names, flag names, subcommand names, or user-facing copy.

Why: Stated preference while porting features from the table-reservation-goat CLI. The cross-network unified-search command in that tool is literally named goat — when porting, pick a different name.

How to apply: When porting table-reservation-goat features, rename the goat command (the cross-network/multi-provider unified search). Either roll its behavior into the existing search command (default to fan-out across all providers, use --provider to scope) or pick a neutral name like find, across, or any. Other trg names (earliest, drift, watch, sync) are fine to keep as-is — only "goat" is off-limits. Also avoid it in docs, help text, and skill copy.

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