Skip to content

Create AGENTS.md with agent instructions - #1944

Open
bmos wants to merge 7 commits into
move-coop:mainfrom
bmos:patch-5
Open

bmos wants to merge 7 commits into
move-coop:mainfrom
bmos:patch-5

Conversation

@bmos

@bmos bmos commented Aug 29, 2026

Copy link
Copy Markdown
Collaborator

Added comprehensive agent instructions covering scope, sources of truth, handling ambiguity, pre-commit guidelines, change discipline, and decisionmaking authority.

Based on the PyPDFForm AGENTS.md file.

What is this change?

  • AI-created pull requests are becoming more frequent, often ignoring pull request templates and project coding standards. Many projects are implementing AI policies to encourage, regulate, or ban the use of AI in coding and/or submission workflows. Along with including reference to the policy in contributor guides, AGENTS.md can be used to help agents follow our best practices and avoid spam, without disallowing the use of AI assistance.

Considerations for discussion

  • Are there other standards / guidelines we should be enforcing?
  • Is there support in the parsons project for requiring humans to write pull requests?
  • Do parsons contributors want to allow the use of AI coding agents?

How to test the changes (if needed)

  • Ask an agent to implement a change to our repo, with this branch checked out.

Breaking Changes

Breaking changes are changes to our public API which may require existing users to change their code. If there are no breaking changes, any existing parsons user should not need to do anything after updating their parsons version.

Does this PR introduce breaking changes?
  • label: Breaking change — This PR introduces one or more breaking changes.
  • label: Non-breaking change — This PR does not introduce one or more breaking changes.

Details (if needed)

  • (List out any changes to the API that may cause breaks for developer implementation.)

@github-actions github-actions Bot added documentation Work type - improvements or additions to documentation non-breaking-change Status - Indicates that the code in this PR does not have any breaking changes. labels Aug 29, 2026
@shaunagm

shaunagm commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

This seems like it deserves more of a community discussion. I know you're not generally available during Parsons Parties, do you want to coordinate a separate time to have a discussion?

@bmos

bmos commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator Author

I can schedule myself to be available, maybe next Thursday?

@shaunagm

shaunagm commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

The 10th? That works for me

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

Coverage report

This PR does not seem to contain any modification to coverable code.

@github-actions github-actions Bot added the github_actions Pull requests that update GitHub Actions code label Sep 10, 2026
Added comprehensive agent instructions covering scope, sources of truth, handling ambiguity, pre-commit guidelines, change discipline, and decisionmaking authority.
Removed PR best practices link from the Sources Of Truth section as agents should not be making PRs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Work type - improvements or additions to documentation github_actions Pull requests that update GitHub Actions code non-breaking-change Status - Indicates that the code in this PR does not have any breaking changes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants