feat: add github-repo-maintainer agent

[jordanpartridge]

Closes #37

Adds .claude/agents/github-repo-maintainer.md with 6 skills:

1. Conflict Resolution
2. Branch Management
3. Test & Validate
4. GitHub Comms
5. Self-Termination
6. Work Discovery

🤖 Generated by Agent B (structured prompt)

Summary by CodeRabbit

• Documentation
  • Added comprehensive guide for the GitHub Repo Maintainer Agent, including operational skill documentation, detailed use-case descriptions, practical examples, and command-line automation guidance for repository management and GitHub operations. Provides workflow patterns and decision frameworks for repository maintainers.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

A new Markdown agent definition document was added describing a GitHub Repo Maintainer Agent with six skill areas: Conflict Resolution, Branch Management, Test Validation, GitHub Communications, Self-Termination, and Work Discovery. Each skill includes descriptions, use-cases, and representative Bash command examples for automation.

Changes

Cohort / File(s)	Summary
GitHub Repo Maintainer Agent Definition \.claude/agents/github-repo-maintainer.md	New agent document specifying six operational skills: conflict resolution (merge handling), branch management (create/delete), test validation (execution), GitHub communications (PR/issue interactions), self-termination (graceful shutdown), and work discovery (task identification via GitHub CLI and Git). Includes concrete command examples and decision points for each skill.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 A new maintainer joins the warren today,
With GitHub wisdom to light the way—
Conflicts resolved with a hop and a bound,
Six shiny skills in this agent I've found!
Branches and tests and PRs galore,
This repo's kept tidy forevermore! 🌟

Pre-merge checks

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat: add github-repo-maintainer agent' accurately and concisely describes the main change: adding a new agent definition file.
Linked Issues check	✅ Passed	The PR implements all six required skills for autonomous PR/issue management as specified in issue #37: Conflict Resolution, Branch Management, Test Validation, GitHub Communications, Self-Termination, and Work Discovery.
Out of Scope Changes check	✅ Passed	The PR only adds the github-repo-maintainer agent definition file with no extraneous changes; all modifications directly support the objective of issue #37.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

.claude/agents/github-repo-maintainer.md (2)

71-87: Consider adding a note about tech-stack specificity for test examples.

The test validation examples use vendor/bin/pest and php gate certify, which are specific to this repository's PHP/Laravel setup. Consider either:

• Adding a brief note that these commands are context-specific to your repository
• Including a generic example (e.g., "run your project's standard test command") as a fallback

This helps future maintainers or other agents understand how to adapt the skill to different tech stacks.

---

1-5: Consider adding a prerequisites and invocation section.

The document would benefit from brief sections covering:

• Prerequisites: GitHub CLI installation, required permissions, environment setup
• Invocation model: How is the agent triggered? (On demand, scheduled, event-driven?)
• Error handling: What should the agent do when it encounters complex conflicts, failing tests, or permission errors?

This would make the agent definition more complete and easier to integrate into automation workflows.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ddd1916 and e5bc5cf.

📒 Files selected for processing (1)

• .claude/agents/github-repo-maintainer.md

🔇 Additional comments (2)

.claude/agents/github-repo-maintainer.md (2)

1-182: Well-structured agent definition that aligns with issue requirements.

The agent specification covers all six skills specified in issue #37 with clear descriptions, practical use-cases, and concrete command examples. The organization and scope are appropriate for autonomous repository maintenance.

---

175-175: The jq syntax is correct as written.

The expression gh pr list --state open --json number,title,updatedAt | jq '.[] | select(.updatedAt < (now - 2592000 | todate))' works properly. GitHub's API returns updatedAt as an ISO 8601 string (YYYY-MM-DDTHH:MM:SSZ), and todate converts the Unix timestamp to the same format. Since ISO 8601 strings are lexicographically ordered, the string comparison correctly filters PRs updated more than 30 days ago. No changes needed.

Likely an incorrect or invalid review comment.