-
Notifications
You must be signed in to change notification settings - Fork 1
Add agent instructions and fix-issue command #126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Add AGENTS.md with devcontainer/gh cli documentation - Symlink CLAUDE.md to AGENTS.md for Claude Code compatibility - Add /project:fix-issue command for GitHub issue workflow - Remove .claude/README.md (not part of memory system) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Reviewer's GuideIntroduces shared agent instructions for the devcontainer/gh CLI, wires them into Claude Code via a CLAUDE.md symlink, and adds a new /project:fix-issue command for GitHub issue handling while cleaning up obsolete Claude docs. Flow diagram for fix-issue command stepsflowchart TD
A[Start /project:fix-issue with ARGUMENTS] --> B[Run pixi run gh issue view ARGUMENTS]
B --> C[Fetch issue details]
C --> D[Extract issue number from URL for commit message]
D --> E[Understand problem and locate relevant code]
E --> F[Implement the fix in code]
F --> G[Run pixi run ci<br/>format, lint, test, coverage]
G --> H{CI successful}
H -- No --> I[Fix issues and rerun pixi run ci]
I --> G
H -- Yes --> J[Commit changes with message referencing issue<br/>example Fixes #123]
J --> K[Run pixi run gh pr create]
K --> L[PR created on GitHub]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey - I've left some high level feedback:
- In
.claude/commands/fix-issue.md, step 2 about extracting the issue number from the URL could be more concrete (e.g., showing how to handle both numeric IDs and full URLs, or usinggh issue view --json number), so agents can reliably construct commit messages without manual parsing ambiguity.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- In `.claude/commands/fix-issue.md`, step 2 about extracting the issue number from the URL could be more concrete (e.g., showing how to handle both numeric IDs and full URLs, or using `gh issue view --json number`), so agents can reliably construct commit messages without manual parsing ambiguity.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Summary
AGENTS.mdwith devcontainer and gh cli documentation for AI agentsCLAUDE.md→AGENTS.mdfor Claude Code compatibility/project:fix-issueslash command for GitHub issue workflow.claude/README.md(not part of Claude's memory system per 2026 standards)Changes
AGENTS.mdCLAUDE.md.claude/commands/fix-issue.md.claude/README.mdTest plan
CLAUDE.mdsymlink works:cat CLAUDE.md/project:fix-issuecommand in Claude Code session🤖 Generated with Claude Code
Summary by Sourcery
Document agent environment usage and add a command for handling GitHub issues directly from Claude.
New Features:
Enhancements:
Documentation: