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

Agent-Skills / artifacts

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

- Applies to artifacts/**. - Inherits the repository root AGENTS.md; this file only adds artifact-specific authority rules. - Treat this subtree as evidence, generated reports, review outputs, and intentionally retained artifacts unless a nearby index or schema proves a file is an authored source or fixture. - Do not add new run logs, ad hoc telemetry, or historical output here as normal source. Convert it to a documented fixture, reference, summary, or allowlisted archive first. - Keep local code/test truth,…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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. Distinctive:

    Treat this subtree as evidence, generated reports, review outputs, and intentionally retained artifacts unless a nearby index or schema …

    line 15
  2. Distinctive:

    Do not add new run logs, ad hoc telemetry, or historical output here as normal source.

    line 18
  3. Distinctive:

    Keep local code/test truth, artifact evidence, PR state, review state, and release-readiness claims separate in closeout language.

    line 21
  4. Very specific:

    Run the narrowest command that reproduces or validates the artifact.

    line 36

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

artifacts Agent Guide

Scope

  • Applies to artifacts/**.
  • Inherits the repository root AGENTS.md; this file only adds artifact-specific authority rules.

Edit Policy

  • Treat this subtree as evidence, generated reports, review outputs, and intentionally retained artifacts unless a nearby index or schema proves a file is an authored source or fixture.
  • Do not add new run logs, ad hoc telemetry, or historical output here as normal source. Convert it to a documented fixture, reference, summary, or allowlisted archive first.
  • Keep local code/test truth, artifact evidence, PR state, review state, and release-readiness claims separate in closeout language.
  • For ownership questions, follow Repo Surface Ownership and Path Ownership Boundaries.

Context Pointers

  • Historical artifact policy: Repo Surface Ownership.
  • Review evidence patterns: artifacts/reviews/**.
  • Generated SDK visual/reference artifacts: artifacts/*.html.

Validation

  • For changed artifact files, prove the owning generator, reader, fixture role, or retention reason before closeout.
  • Run the narrowest command that reproduces or validates the artifact. If the generator cannot run, report blocked and keep the artifact claim bounded to manual inspection.

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