Skip to content

[Repo Assist] docs: add AGENTS.md with project conventions for AI coding assistantsΒ #136

@github-actions

Description

@github-actions

πŸ€– This is an automated PR from Repo Assist.

Summary

This PR adds an AGENTS.md file β€” a conventions guide specifically aimed at AI coding assistants (and human contributors) working on this repository.

Why AGENTS.md?

Without this file, AI tools must rediscover project conventions on every run by reading source files. More critically, they repeatedly attempt changes that cannot succeed β€” such as opening PRs that modify package.json (a protected file), then creating issues asking a maintainer to apply the change manually. AGENTS.md short-circuits that wasted cycle.

What It Documents

  • Protected files: package.json and .github/workflows/** cannot be modified by automated PRs β€” create an issue instead
  • Test infrastructure: how to run the unit test suite (node --test test/unit.test.js); which tests work headless vs require VS Code
  • Coding conventions: CommonJS, 4-space indentation, no new runtime dependencies, match surrounding style
  • Architecture notes: PHPCBF class layout, temp file lifecycle, why lib/utils.js must stay free of vscode imports
  • PR checklist: run tests, keep PRs focused, document any required package.json changes in the issue

Test Status

βœ” findFiles (7/7 passing, 63ms) β€” no regressions

Documentation-only change; no runtime code was modified.

Generated by Repo Assist Β· β—·

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@346204513ecfa08b81566450d7d599556807389f

Warning

πŸ›‘οΈ Protected Files

This was originally intended as a pull request, but the patch modifies protected files: AGENTS.md.

These files may affect project dependencies, CI/CD pipelines, or agent behaviour. Please review the changes carefully before creating the pull request.

Click here to create the pull request once you have reviewed the changes

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions