agentleFS
Sign inStart free
BlockKnown publisherblock/builder-syndicate/specs/AGENTS.md

builder-syndicate / specs

AGENTS.md6 starsChanged 8 months agoApache-2.0View on GitHub

The gh CLI doesn't support issue dependencies directly. Use the REST API:

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository3 other files it gives its agents.

The file

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

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Dependencies: Use native GitHub relationships (not text)

    line 25
  2. Distinctive:

    Keep OSS/architectural notes in body (they're requirements)

    line 45

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

Specs - Agent Guide

GitHub Issue Management

Issue Format

{Description paragraph}

## ✅ Acceptance Criteria

- [ ] Testable behavior 1
- [ ] Testable behavior 2

### Internal Coding

`{TASK_ID}`

- Implementation hint 1
- Implementation hint 2

Required Metadata

  • Label: ex machina on all AI-created issues
  • Milestone: Assign to appropriate milestone (e.g., micro steel thread)
  • Dependencies: Use native GitHub relationships (not text)

Creating Dependency Relationships

The gh CLI doesn't support issue dependencies directly. Use the REST API:

# Get issue ID (not issue number)
gh api repos/{owner}/{repo}/issues/{number} --jq '.id'

# Create blocked_by relationship (use -F for integer, not -f)
gh api repos/{owner}/{repo}/issues/{issue_number}/dependencies/blocked_by \
  -X POST \
  -H "X-GitHub-Api-Version: 2022-11-28" \
  -F issue_id={blocking_issue_id}

Task Files

  • Task files in tasks/ are source of truth for issue content
  • Move implementation hints (file paths) to ### Internal Coding footer
  • Keep OSS/architectural notes in body (they're requirements)
  • Title: human-readable, no "feat:" prefix or task ID

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