agentleFS
Sign inStart free
docxologydocxology/codomyrmex/.github/ISSUE_TEMPLATE/AGENTS.md

codomyrmex / ISSUE_TEMPLATE

AGENTS.md10 starsChanged 38 days agoMITView on GitHub

Status: Active | Last Updated: March 2026 Structured GitHub issue forms for bug reports, feature requests, documentation issues, and Jules agent task dispatch.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Use gh issue create with --template flag matching the appropriate template type

    line 23
  2. Very specific:

    Use jules_task.yml for dispatching work to Jules AI agents

    line 30

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

.github/ISSUE_TEMPLATE — AI Agent Guide

Status: Active | Last Updated: March 2026

Purpose

Structured GitHub issue forms for bug reports, feature requests, documentation issues, and Jules agent task dispatch.

Template Inventory

FileTypeLabels Applied
bug_report.ymlBug report formbug, needs-triage
feature_request.ymlFeature request formenhancement, needs-triage
documentation.ymlDocumentation issue formdocumentation, needs-triage
jules_task.ymlJules agent task dispatchjules, agent-task, automated

AI Agent Guidelines

When Creating Issues

  • Use gh issue create with --template flag matching the appropriate template type
  • Bug reports require: environment info, reproduction steps, expected vs actual behavior
  • Feature requests require: problem statement, proposed solution, acceptance criteria
  • Documentation issues require: affected doc file, description of inaccuracy or gap

Jules Task Dispatch

  • Use jules_task.yml for dispatching work to Jules AI agents
  • Select target module(s) from the 28+ available options
  • Choose task type: module improvement, bug fix, code health, tests, etc.
  • Set priority (Low/Medium/High/Critical)
  • Or use the batch dispatch: gh workflow run jules-dispatch.yml

Naming Conventions

  • Bug titles: [Bug]: <brief description of unexpected behavior>
  • Feature titles: [Feature]: <brief description of capability>
  • Docs titles: [Docs]: <affected file or section> — <problem>
  • Jules titles: [Jules]: <task type> — <module name>

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