agentleFS
FmarzochiFmarzochi/EGC/.cursor/rules/golang-hooks.md

EGC / rules

Cursor rule61 starsChanged 46 days agoApache-2.0View on GitHub

Go hooks extending common rules

We split this golang-hooks.md into the rules it gives an agent

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

  • 1

    Very specific

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

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

    go vet: Run static analysis after editing .go files

    line 15
  2. Distinctive:

    staticcheck: Run extended static checks on modified packages

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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
golang-hooks.md

Go Hooks

This file extends the common hooks rule with Go specific content.

PostToolUse Hooks

Configure in ~/.gemini/settings.json:

  • gofmt/goimports: Auto-format .go files after edit
  • go vet: Run static analysis after editing .go files
  • staticcheck: Run extended static checks on modified packages

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.

Reviews can't be read right now.

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.