GitHub user Yicong-Huang edited a comment on the discussion: AI-generated descriptions in issues and PRs
While we welcome AI-assisted contributions, agents do tend to produce overly verbose issues, pull request descriptions, and comments. Here are my thinkings from a few perspectives: - **From a project-management perspective:** A general hard limit on the length of descriptions or comments would not be ideal. These interfaces are used by both agents and humans, and humans sometimes have legitimate reasons to provide longer explanations. - **For agents:** Contributors should instruct their agents to write concisely. We can reinforce this in two ways: 1. State our expectations more firmly in `AGENTS.md`. 2. Build and use agent tooling with built-in safeguards. I created a [Texera development agent plugin](https://github.com/Texera/texera-agent-plugins) (currently in a private repository) with `open-issue` and `open-pr` skills that include a verbosity gate to prevent unnecessarily long content. I am testing it with several recent issues: - #7136, - #7393, - #7135 and PRs: - #7137 - #7427 - #7172 Please let me know what you think. The same verbosity gate will also apply to AI-assisted PR reviews performed using the Texera agent plugin. - **For humans:** Although we should not impose strict length limits, encouraging concise writing would improve communication. We could add guidance to `CONTRIBUTING.md` recommending that issues, pull requests, and comments remain focused. Related guidance could discourage including unnecessary implementation details in issue descriptions. These should remain recommendations rather than hard requirements, which would also be difficult to enforce technically. - **For reviewers:** When a description or comment is excessively long, reviewers should feel comfortable asking the author to revise it for clarity and conciseness. GitHub link: https://github.com/apache/texera/discussions/7377#discussioncomment-17945335 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
