agentleFS
Edmonds-Commerce-LimitedEdmonds-Commerce-Limited/claude-code-hooks-daemon/src/CLAUDE.md

claude-code-hooks-daemon / src

CLAUDE.md4 starsChanged 16 days agoMITView on GitHub

IF YOU ARE WORKING ON A PROJECT THAT HAS HOOKS DAEMON INSTALLED — YOU MUST NOT EDIT ANYTHING IN THIS FOLDER. This is the daemon's own source code: an upstream dependency, not part of your project. Editing files here breaks your installation, is overwritten on the next daemon update, and creates conflicts that prevent future upgrades. Unless this repository IS the daemon. In self-install (dogfood) mode the daemon's source and the project are the same checkout, so there is no…

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NOT EDIT ANYTHING IN THIS FOLDER.

    line 4

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
CLAUDE.md

DO NOT EDIT - Hooks Daemon Internal Source Code

IF YOU ARE WORKING ON A PROJECT THAT HAS HOOKS DAEMON INSTALLED — YOU MUST NOT EDIT ANYTHING IN THIS FOLDER.

This is the daemon's own source code: an upstream dependency, not part of your project. Editing files here breaks your installation, is overwritten on the next daemon update, and creates conflicts that prevent future upgrades.

Unless this repository IS the daemon. In self-install (dogfood) mode the daemon's source and the project are the same checkout, so there is no upstream to be overwritten by and editing here is the normal way to work — see SELF_INSTALL.md. The heading above is addressed to a CLIENT project that installed the daemon under .claude/hooks-daemon/; it is not a claim that these files are untouchable everywhere. Check which case you are in before concluding an instruction to edit src/ is a mistake: two sub-agents working on daemon source have now read this page as forbidding their assigned task, and one classified it as injected content.

Do This Instead

  • Custom handler behaviour — create project-level handlers in YOUR repo (.claude/hooks-daemon/bin/hooks-daemon init-project-handlers scaffolds them; they are auto-discovered). See Project-Level Handlers Guide.
  • Found a bug — do NOT fix it here. Use the hooks-daemon skill with args issue-report, or read the Bug Reporting Guide; working notes go under untracked/scratch/ (see explain-handler project_containment for why not a temp path).
  • Change handler configuration — edit your project's .claude/hooks-daemon.yaml (that IS yours: enable/disable handlers, set priorities and options).
  • Understand how something works — read the docs, not the source: ARCHITECTURE.md, HANDLER_DEVELOPMENT.md, PROJECT_HANDLERS.md, DEBUGGING_HOOKS.md.

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.