agentleFS
omarshahineomarshahine/findmy-cli/AGENTS.md

findmy-cli

AGENTS.md62 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-findmy-cli/memory during the AGENTS.md migration. Keep this section current when project-specific operating knowledge changes. omarshahine/homebrew-tap (cloned at ~/GitHub/homebrew-tap) holds 6 formulas, each built…

  • Reads credentials
  • 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.

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
  1. 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

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

<!-- BEGIN CLAUDE MEMORY IMPORT: -Users-omarshahine-GitHub-findmy-cli -->

Imported Claude Project Memory

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

memory/MEMORY.md

  • Homebrew tap auto-bump — 6 formulas self-update on v* tag via per-repo workflow + HOMEBREW_TAP_TOKEN (in chezmoi)

memory/homebrew-tap-autobump.md


name: homebrew-tap-autobump description: How omarshahine/homebrew-tap formulas auto-update on release metadata: node_type: memory type: project originSessionId: be5786e9-1fd7-4b4a-9486-e20512188e64

omarshahine/homebrew-tap (cloned at ~/GitHub/homebrew-tap) holds 6 formulas, each built from the source tarball (no bottles):

  • findmy-cli (Go+Swift), aqara-cli (Python), lutron-cli (Python), apple-pim-cli (Swift), daikin-cli (Go), trakt-cli (Go)

Each source repo has .github/workflows/publish-homebrew.yml that, on every v* tag, computes the GitHub source tarball sha256 and pushes a url+sha256 bump to the tap. The workflow only updates the first app url/sha256 pair, so vendored resource blocks (Python deps in aqara/lutron, swift-argument-parser in apple-pim) are left untouched — correct, since those change independently of app version.

Gated on repo secret HOMEBREW_TAP_TOKEN: a fine-grained PAT scoped ONLY to homebrew-tap with Contents: read/write (the default GITHUB_TOKEN can't push cross-repo). Stored in chezmoi as HOMEBREW_TAP_TOKEN in ~/.secrets-macbook-pro.env. The SAME token value is set as a secret on all 6 source repos — reusable because it grants access to the tap, not the source repo.

To add a new project to the tap: write the formula, copy publish-homebrew.yml (set FORMULA_PATH to the formula name, which may differ from repo name — e.g. repo trakt-plugin → Formula/trakt-cli.rb, repo apple-pim → Formula/apple-pim-cli.rb), then printf '%s' "$HOMEBREW_TAP_TOKEN" | gh secret set HOMEBREW_TAP_TOKEN --repo omarshahine/<repo> after sourcing the env.

apple-pim-cli formula note: Homebrew's build sandbox blocks network, so the formula vendors swift-argument-parser as a resource and inreplaces Package.swift to a local .package(path:) for an offline swift build. Verified to compile all 4 binaries (calendar/reminder/contacts/mail-cli).

<!-- END CLAUDE MEMORY IMPORT: -Users-omarshahine-GitHub-findmy-cli -->

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.