agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.cursor/rules/fleet-repo-intelligence.mdc

mac-yolo-safeguards / rules

Cursor rule3 starsChanged 3 days agoMITView on GitHub

Prefer fleet local semantic repo intelligence (grepai / hermes-context) before cold codebase exploration

The file

We split this fleet-repo-intelligence.mdc into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 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.

  • 3

    Very specific

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

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

    Before cold rg/find exploration of unfamiliar areas of this monorepo:

    line 9
  2. Very specific:

    Prefer MCP grepai_* tools (repo .mcp.json → isolated index of main).

    line 11
  3. Very specific:

    Do not run grepai watch from a multi-worktree checkout (indexes all worktrees and hammers Ollama).

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule 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
fleet-repo-intelligence.mdc
---
description: Prefer fleet local semantic repo intelligence (grepai / hermes-context) before cold codebase exploration
globs:
alwaysApply: true
---

# Fleet repo intelligence (JetBrains Context local equivalent)

Before cold `rg`/`find` exploration of unfamiliar areas of this monorepo:

1. Prefer **MCP `grepai_*` tools** (repo `.mcp.json` → isolated index of `main`).
2. Or CLI: `grepai search "…"` from `~/.hermes/semantic-index/mac-yolo-safeguards`.
3. Multi-repo: `hermes-context search "…"`.
4. Structure: `.graphify-venv/bin/graphify query "…"` when `graphify-out/graph.json` exists.

Do **not** run `grepai watch` from a multi-worktree checkout (indexes all worktrees and hammers Ollama). Refresh only via `bash tools/install-fleet-repo-intelligence.sh`.

Status: `node tools/fleet-repo-intelligence-status.js`

Official `jbcontext` (JetBrains Context) is optional/not required for this fleet.

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.