Find the daemon that fits your team’s operational debt

Browse by the problem you need solved, the systems involved, or daemon operating mode. These use cases map common engineering hygiene gaps to concrete daemon configurations.

Filter catalog

Select one or more options in any group to narrow the use case catalog. Filters combine across groups.

By tools
By problem
By daemon type

Showing all use cases

Use case matches

Keep PRs mergeable and CI-green

Unblock merge conflicts, flaky checks, and lockfile drift without changing PR intent or scope.

Best-fit daemon
PR Mergeability
Daemon type
watch-only
Systems/tools
  • GitHub
  • CI
View daemon markdown
.agents/daemons/pr-mergeability/DAEMON.md
---
id: pr-mergeability
purpose: Keep non-draft pull requests mergeable and CI-green without changing PR intent/scope, while staying anchored to one trigger context per run.
watch:
  - Branch sync and update events on non-draft PRs.
  - Check-status signals on non-draft PRs for checks that affect mergeability.
routines:
  - Resolve mechanical merge conflicts when the safe resolution is clear and preserves PR intent/scope.
  - Apply low-risk mergeability fixes: snapshot updates, lockfile drift fixes, lint autofix, and flaky-test retries when tied to the trigger context.
  - Escalate semantic/intention conflicts between base and branch instead of auto-resolving.
deny:
  - When triggered by a check-status signal, do not fix or comment on unrelated failing checks.
  - Do not open new pull requests or new issues.
  - Do not review, approve, or request changes on pull requests.
  - Do not implement review-comment suggestion patches.
  - Do not make changes beyond mergeability maintenance.
---

Keep PR metadata current and linked

Maintain PR titles, required body sections, and issue references so reviewers always have context.

Best-fit daemon
PR Metadata
Daemon type
watch-only
Systems/tools
  • GitHub
  • Linear
View daemon markdown
.agents/daemons/pr-metadata/DAEMON.md
---
id: pr-metadata
purpose: Keep pull request title and body metadata complete, current, and linked to the correct issue-tracker item.
watch:
  - Wake on pull request opened, edited, reopened, and synchronize events.
  - Wake on pull request review comments or mentions requesting title or body metadata updates.
routines:
  - Verify the pull request title ends with the linked issue identifier and patch only the suffix when it is missing or stale.
  - Ensure the pull request body includes current sections for primary changes, reviewer walkthrough, correctness and invariants, and testing and QA.
  - Ensure the pull request body ends with an explicit issue reference like Resolves <ISSUE-1234>.
deny:
  - Do not approve, merge, close, or reopen pull requests.
  - Do not edit source code, tests, CI config, labels, reviewers, assignees, milestones, or other non metadata fields.
  - Do not rewrite the whole pull request body when targeted section patches are sufficient.
---

Triage PR review feedback

Classify, deduplicate, and resolve review feedback threads so signal stays high as code evolves.

Best-fit daemon
PR Review Triage
Daemon type
watch-only
Systems/tools
  • GitHub
View daemon markdown
.agents/daemons/pr-review-triage/DAEMON.md
---
id: pr-review-triage
purpose: Keep pull request review feedback threads accurate by requiring explicit correctness triage, handling duplicate/conflicting feedback, and resolving fixed feedback safely with GitHub-only thread actions.
watch:
  - Wake on every pull request review submission event from non-Charlie authors (human or bot).
  - Wake on every pull request review comment event from non-Charlie authors (human or bot).
  - Wake on pull request synchronize/update events (new commits pushed to the PR branch) to re-check unresolved review feedback after code changes.
routines:
  - For every actionable review feedback thread, produce an explicit correctness triage decision (valid, invalid, or uncertain) with rationale.
  - Evaluate review feedback in the triggering pull request to detect semantic duplicates and conflicting guidance.
  - Reply on duplicate feedback with a link to the canonical feedback item and a short duplicate rationale.
  - Reply on conflicting feedback with which guidance appears correct and why.
  - After commits are pushed, detect whether unresolved feedback has been addressed in code and resolve the corresponding thread only when confidence is medium or high.
deny:
  - Do not take actions outside GitHub.
  - Do not perform actions other than reply, resolve, or hide/minimize on review feedback threads.
  - Do not approve, request changes, dismiss reviews, or change pull request state.
  - Do not edit code, push commits, or open new pull requests/issues.
  - Do not autonomously resolve or hide/minimize feedback when confidence is low.
---