[timmoon10]

Description

This is an attempt to avoid some annoying habits in agent-generated code.

Type of change

• Documentation change (change only to the documentation, either a fix or a new content)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Infra/Build change
• Code refactoring

Changes

• Add code quality guidelines to AGENTS.md

Checklist:

• I have read and followed the contributing guidelines
• The functionality is complete
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[greptile-apps]

Confidence Score: 5/5

[Low impact] The documentation change appears safe to merge.

Summary

Adds code quality guidelines to AGENTS.md.

• Contributors and coding agents now have guidance for writing readable, focused code.

_{Reviews (1) · Last reviewed commit: "Add code quality guidelines to AGENTS.md" · Reviewed by Greptile}

[ksivaman]

👍

[ksivaman]

Happy to merge but I'm wondering if it would make a difference.

Do you have any example before and after with this? This repo has defined a lot of predefined skills, including for code review and quality here, perhaps it is also something to look at.