updated AGENTS.md with instructions to create PRs

[metachris]

No description provided.

[claude]

Claude finished @metachris's task in 1m 0s —— View job

---

PR Review: AGENTS.md Implementation Workflow

This PR adds clear instructions for LLMs to follow a complete implementation workflow when asked to implement something. The instructions emphasize creating feature branches, committing, pushing, and creating PRs.

Summary

Overall: Good addition that provides clear guidance for LLMs working with this repository.

✅ What looks good:

• Clear, step-by-step workflow instructions
• Emphasis on completing the full workflow (not stopping at providing links)
• Good branch naming convention example (claude/issue-123-add-feature)
• Proper guidance to reference issue numbers in PR descriptions

📝 Minor issue found:

• Typo on line 57: 1.. should be 1. (I've left an inline comment with a suggestion)

💡 Potential improvements to consider:

• The formatting of step 1 is slightly inconsistent - the sub-bullets under 1.. use dashes instead of sub-numbering (e.g., 1a., 1b.)
• Consider adding a step to verify lint/tests pass before creating the PR (e.g., make lt)

---

• Analyze the PR changes
• Review code quality and best practices
• Check for bugs, security issues, and performance concerns
• Provide feedback

[claude]

Claude finished @metachris's task in 41s —— View job

---

PR Review: AGENTS.md Implementation Workflow

This PR adds clear instructions for LLMs to follow a complete implementation workflow when asked to implement something. The latest commit (50085dc) fixes the typo that was previously identified.

• Analyze the PR changes
• Review code quality and best practices
• Check for bugs, security issues, and performance concerns
• Provide feedback

Summary

Overall: This is a good addition that provides clear guidance for LLMs working with this repository.

✅ What looks good:

• Clear, step-by-step workflow instructions
• Emphasis on completing the full workflow (not stopping at providing links)
• Good branch naming convention example (claude/issue-123-add-feature)
• Proper guidance to reference issue numbers in PR descriptions
• The typo (1.. → 1.) from the previous commit has been fixed ✓

💡 Suggestions for consideration:

• The sub-bullets under step 1 use a different format (dashes) compared to the numbered list. For better clarity, consider indenting them as proper sub-items:

  1. Create a feature branch
     - based on the latest `main` branch
     - use descriptive branch names like `claude/issue-123-add-feature`

• Consider adding a step to verify lint/tests pass before creating the PR (e.g., make lt) to ensure CI passes

These are minor stylistic suggestions and not blocking. The PR achieves its goal of providing clear instructions for LLMs.

Recommendation: Approve ✅