Doc Revision: Contributing

[markstur]

I'm adding this on behalf of some doc feedback... The notes are a bit raw... The gist is we should have a policy about AI use in PRs (whatever it might be) and make that visible in our contributors docs, repos, maybe PR template.

Summary of Requested Changes:

AI Agent contributions… this is a new problem. We need popular OSS repos to make a maintainer supported statement regarding use of agents.
example scenario matplotlib/matplotlib#31132
happens a lot now.. agents pushing PRs/commits..
this and the obvious other issue of devs generating code from claude/gemini/… and not attributing

Example: https://github.com/ggml-org/llama.cpp/blob/master/AGENTS.md#guidelines-for-contributors-using-ai

I’d start to describe a loose restriction policy, but leave it blank and refer to an issue/discussion thread .. maybe set up a chat
this is “blowing” up right now

there are some suggestions.. but if it’s truly OSS the maintainers should decide in an open way

Requirements
Enter the requirements that would warrant success for this issue.

Task Checklist

• Contributing Guideline Compliance: I read and complied by "Documentation Contribution Guidelines" section of the Agent Stack project CONTRIBUTING.md guide.
• Snippet Test: Verified all code works in a fresh environment (fresh agent stack install and clean environment).
• Visual Preview: Checked formatting/layout via Mintlify.
• CLI Sync: Ran mise run agentstack-cli:docs (if applicable).
• Location: Updates placed in docs/development for go live during next release or both docs/development and docs/stable for urgent go live.

[dosubot]

Hi, @markstur. I'm Dosu, and I'm helping the agentstack team manage their backlog and am marking this issue as stale.

Issue Summary

• You requested a documentation update to the Contributing guide so the repo clearly states its policy on AI/agent-generated contributions.
• The request specifically calls out PRs and code attribution, with the goal of making the contribution policy visible to contributors.
• There hasn’t been any maintainer follow-up or discussion yet, so no final policy decision has been recorded in the issue.
• The likely path forward is to add clear guidance in contributor docs, with optional reinforcement via a PR template or repo-level notice.

Next Steps

• Please let us know if this is still relevant to the latest version of the agentstack repository.
• If it is, you can keep the discussion open by commenting here; otherwise, this issue will be automatically closed in 7 days.

Thanks for your understanding and contribution.