agentleFS
Sign inStart free
jscraikjscraik/Agent-Skills/logs/AGENTS.md

Agent-Skills / logs

AGENTS.md9 starsChanged 46 days agoApache-2.0View on GitHub

- Treat this subtree as local run output unless a tracked file has an explicit fixture, archive, or reader contract. - Do not commit raw logs, secrets, tokens, private telemetry, or bulky local traces. Promote only distilled summaries, fixtures, or policy evidence with a retention reason. - Redact sensitive content before using logs in docs, PR bodies, or review artifacts. - Before staging anything under logs/**, identify its owner, reader, retention reason, and whether it should be a fixture or…

The file

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

4 rules. About 1 is common, 2 are distinctive, and 1 is very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Treat this subtree as local run output unless a tracked file has an explicit fixture, archive, or reader contract.

    line 14
  2. Common:

    Do not commit raw logs, secrets, tokens, private telemetry, or bulky local traces.

    line 16
  3. Very specific:

    Before staging anything under logs/, identify its owner, reader, retention reason, and whether it should be a fixture or ignored runtime …

    line 29
  4. Distinctive:

    If no durable role exists, leave the log untracked and summarize the evidence elsewhere.

    line 31

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

logs Agent Guide

Scope

  • Applies to logs/**.
  • Inherits the repository root AGENTS.md.

Edit Policy

  • Treat this subtree as local run output unless a tracked file has an explicit fixture, archive, or reader contract.
  • Do not commit raw logs, secrets, tokens, private telemetry, or bulky local traces. Promote only distilled summaries, fixtures, or policy evidence with a retention reason.
  • Redact sensitive content before using logs in docs, PR bodies, or review artifacts.

Context Pointers

  • Repo surface ownership: ../Docs/agents/15-repo-surface-ownership.md.
  • Security and governance: ../Docs/agents/06-security-and-governance.md.

Validation

  • Before staging anything under logs/**, identify its owner, reader, retention reason, and whether it should be a fixture or ignored runtime state.
  • If no durable role exists, leave the log untracked and summarize the evidence elsewhere.

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