codomyrmex / workflows
AGENTS.md10 starsChanged 38 days agoMITView on GitHub
Status: Active | Last Updated: July 2026 GitHub Actions workflow definitions for CI/CD, security, multi-agent infrastructure, documentation, benchmarks, PR automation, and repository maintenance. 37 workflows total.
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,700 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 repository47 other files it gives its agents.
- .agent/AGENTS.mdAGENTS.md
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .agents/skills/agent-interop/AGENTS.mdAGENTS.md
- .agents/skills/AGENTS.mdAGENTS.md
- .agents/skills/first-principles/AGENTS.mdAGENTS.md
- .agents/skills/mcp-tool-use/AGENTS.mdAGENTS.md
- .agents/skills/red-team/AGENTS.mdAGENTS.md
- .agents/skills/systems-thinking/AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- config/AGENTS.mdAGENTS.md
- .cursor/skills/AGENTS.mdAGENTS.md
- .cursor/skills/codomyrmex/AGENTS.mdAGENTS.md
- .cursor/skills/desloppify/AGENTS.mdAGENTS.md
- .cursor/skills/fractals/AGENTS.mdAGENTS.md
- data/AGENTS.mdAGENTS.md
- .devcontainer/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- evaluations/AGENTS.mdAGENTS.md
- examples/AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- .github/commands/AGENTS.mdAGENTS.md
- .github/ISSUE_TEMPLATE/AGENTS.mdAGENTS.md
- .github/scripts/AGENTS.mdAGENTS.md
- .jules/AGENTS.mdAGENTS.md
- .pipelines/AGENTS.mdAGENTS.md
- projects/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- src/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- .workflows/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-interopSkill
- first-principlesSkill
- mcp-tool-useSkill
- red-teamSkill
- systems-thinkingSkill
- agent-interopSkill
- first-principlesSkill
- mcp-tool-useSkill
- qmdSkill
- red-teamSkill
- systems-thinkingSkill
- CodomyrmexSkill
- desloppifySkill
- Fractals orchestratorSkill
- CodomyrmexSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 108
Read the full workflow file
- Very specific: line 110
Keep the Windows portability paths explicit and use cross-platform commands (or declare shell: bash when Bash syntax is unavoidable)
- Distinctive: line 112
Verify action versions don't change interface
≈ “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.
Files
<!-- markdownlint-disable MD060 -->.github/workflows — AI Agent Guide
Status: Active | Last Updated: July 2026
Purpose
GitHub Actions workflow definitions for CI/CD, security, multi-agent infrastructure, documentation, benchmarks, PR automation, and repository maintenance. 37 workflows total.
Workflow Inventory
Core CI/CD
| File | Trigger | Key Jobs |
ci.yml | push/PR main,develop | lint, coverage-gate, Unix full-suite matrix, Windows portability matrix, build |
pre-commit.yml | push/PR | pre-commit, commit-message-check and repository consistency checks |
security.yml | schedule daily + push | dependency-scan, bandit, semgrep, codeql, trufflehog |
release.yml | tag v*.*.* | quality-gate (60% cov), build, PyPI publish, stable-release documentation PR |
Agent & PR Infrastructure
| File | Trigger | Purpose |
auto-merge.yml | check_suite, label | Squash-merge PRs a reviewer labelled auto-merge once every check passes (never applied by automation) |
pr-labeler.yml | PR opened/sync | Auto-label by paths, branch, size, module |
pr-title-check.yml | PR open/edit/sync | Enforce Semantic/Conventional Commits for PR titles |
auto-assign.yml | PR opened | Auto-assign PR creator as assignee |
pr-conflict-check.yml | push main, every 6h | Detect + label conflicting PRs |
pr-linter-comments.yml | PR opened/sync | Post inline Ruff linter comments on changed files |
pr-coverage-comment.yml | CI complete | Post coverage delta and missing test lines |
agent-welcome.yml | PR opened | Agent-specific welcome message + checklist |
agent-metrics.yml | weekly Monday | Agent PR/issue/workflow health dashboard |
jules-dispatch.yml | workflow_dispatch | Batch create Jules task issues |
Community & Release Automation
| File | Trigger | Purpose |
first-interaction.yml | Issue/PR opened | Greet first-time contributors with helpful links |
first-pr-merged.yml | PR closed (merged) | Post congratulatory welcome on first merged PR |
release-drafter.yml | push main | Auto-draft release notes based on PR labels |
Documentation
| File | Trigger | Purpose |
documentation.yml | doc file changes | Build and deploy to GitHub Pages |
documentation-validation.yml | PR + weekly | Link check, structure validation |
docs-deploy.yml | tag v*, manual | Strict MkDocs build only, no publication: GitHub Pages belongs to documentation.yml. make docs-check runs the same mkdocs build --strict on PRs |
Repository Health
| File | Trigger | Purpose |
code-health.yml | push main, weekly Sunday | Coverage trends, ruff stats |
benchmarks.yml | push main, weekly Wed | Performance regression tracking |
maintenance.yml | weekly Sunday | Stale issues/PRs, artifact cleanup |
cleanup-branches.yml | weekly | Delete merged + stale branches |
lock-threads.yml | weekly Sunday | Lock 90d issues, 60d PRs |
Orchestration
| File | Trigger | Purpose |
workflow-coordinator.yml | push/PR | Smart path-based triggering |
workflow-status.yml | workflow_run | Status dashboard |
Gemini AI
| File | Trigger | Purpose |
gemini-dispatch.yml | various | Route @gemini-cli commands |
gemini-review.yml | PR opened | AI code review |
gemini-triage.yml | issue opened | AI issue triage |
gemini-scheduled-triage.yml | weekly | Batch triage unlabeled issues |
gemini-invoke.yml | manual dispatch | On-demand Gemini analysis |
Critical Design Decisions
- Workflows declare a top-level
permissions:block. 31 of 37 do today (12 of thempermissions: {}); the 6 without one inherit the repository default and need a block. astral-sh/setup-uvis the standard for all UV installations, pinned by full commit SHA with the release named in a trailing comment.- CI runs Ubuntu/Python 3.11 plus Windows/Python 3.11 on PRs. Main pushes run the full suite on Ubuntu and macOS across Python 3.11–3.14, plus the blocking Windows portability contract across Python 3.11–3.13.
- Ruff, ty, import layering, package build, dependency validation, and the primary test/coverage gates are authoritative. Optional PR commentary and benchmark/health reporting jobs remain informational.
- Documented coverage floor is 60% (
fail_underinpyproject.toml). The Unix unit matrix andcoverage-gatejobs pass--cov-fail-under=60and fail on breach. The Windows portability matrix is a scoped platform contract, so it emits JUnit evidence without pretending to measure repository-wide coverage.release.ymluses--cov-fail-under=60. Default localuv run pytestomits--covfor speed. - Jules PRs are exempt from stale closure (90d stale, 14d close)
AI Agent Guidelines
Safe to Read
- Any workflow file to understand triggers, jobs, and permissions
yamllintoutput to check syntax before suggesting edits
Before Modifying Any Workflow
- Read the full workflow file
- Preserve all
permissions:blocks - Keep the Windows portability paths explicit and use cross-platform commands
(or declare
shell: bashwhen Bash syntax is unavoidable) - Verify action versions don't change interface
- Stage changes on a feature branch, not directly on main
Common Patterns
uv sync --locked --group docs --all-extras --devinstalls the locked test profile; the explicitdocsgroup is required because documentation-hook tests import MkDocs.if: always()is limited to report/status jobs; required checks must preserve the underlying failure result and be enforced by their final status job.if: always()on summary jobs ensures they run after failurescontinue-on-error: trueon lint/format steps for agent flexibility
Currency and supply chain
Account rules CUR-1..CUR-16 are authoritative for this repository; where this file and those rules disagree, the rules win.
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
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.

