Flag documentation drift from merged PRs weekly

Tools

Hermes Agent

Overview

Copy-paste blueprints for common automation patterns.

Workflow

Copy-paste blueprints for common automation patterns. Each blueprint uses Hermes's built-in cron scheduler for time-based triggers and webhook platform for event-driven triggers. Every blueprint works with any model — not locked to a single provider. For parameterized blueprints with forms instead of cron syntax, see the Automation Blueprints Catalog. All three support delivery to Telegram, Discord, Slack, SMS, email, GitHub comments, or local files. Development Workflow​ Nightly Backlog Triage​ Label, prioritize, and summarize new issues every night. Delivers a digest to your team channel. Trigger: Schedule (nightly) Automatic PR Code Review​ Review every pull request automatically when it's opened. Posts a review comment directly on the PR. Trigger: GitHub webhook Option A — Dynamic subscription (CLI): Option B — Static route (config.yaml): Then in GitHub: Settings → Webhooks → Add webhook → Payload URL: http://your-server:8644/webhooks/github-pr-review, Content type: application/json, Secret: github-webhook-secret, Events: Pull requests. Docs Drift Detection​ Weekly scan of merged PRs to find API changes that need documentation updates. Trigger: Schedule (weekly) Dependency Security Audit​ Daily scan for known vulnerabilities in project dependencies. Trigger: Schedule (daily) DevOps & Monitoring​ Deploy Verification​ Trigger smoke tests after every deployment. Your CI/CD pipeline POSTs to the webhook when a deploy completes. Trigger: API call (webhook) Your CI/CD pipeline triggers it: Alert Triage​ Correlate monitoring alerts with recent changes to draft a response. Works with Datadog, PagerDuty, Grafana, or any alerting system that can POST JSON. Trigger: API call (webhook) Uptime Monitor​ Check endpoints every 30 minutes. Only notify when something is down. Trigger: Schedule (every 30 min) Research & Intelligence​ Competitive Repository Scout​ Monitor competitor repos for interesting PRs, features, and architectural decisions. Trigger: Schedule (daily) AI News Digest​ Weekly roundup of AI/ML developments. Trigger: Schedule (weekly) Paper Digest with Notes​ Daily arXiv scan that saves summaries to your note-taking system. Trigger: Schedule (daily) GitHub Event Automations​ Issue Auto-Labeling​ Automatically label and respond to new issues. Trigger: GitHub webhook CI Failure Analysis​ Analyze CI failures and post diagnostics on the PR. Trigger: GitHub webhook Auto-Port Changes Across Repos​ When a PR merges in one repo, automatically port the equivalent change to another. Trigger: GitHub webhook Business Operations​ Stripe Payment Monitoring​ Track payment events and get summaries of failures. Trigger: API call (webhook) Daily Revenue Summary​ Compile key business metrics every morning. Trigger: Schedule (daily) Multi-Skill Workflows​ Security Audit Pipeline​ Combine multiple skills for a comprehensive weekly security review. Trigger: Schedule (weekly) Content Pipeline​ Research, draft, and prepare content on a schedule. Trigger: Schedule (weekly) Quick Reference​ Cron Schedule Syntax​ Delivery Targets​ Webhook Template Variables​ The [SILENT] Pattern​ When a cron job's response contains [SILENT], delivery is suppressed. Use this to avoid notification spam on quiet runs: This means you only get notified when the agent has something to report.

Reported result

The source does not report measured outcomes, success rates, or specific failures for this workflow. It only describes the intended behavior: detecting documentation drift and delivering alerts via Telegram. A measurable acceptance check would be verifying that the agent correctly identifies a known documentation gap in a test PR and suppresses notifications when no gaps exist.

Human role

The original post does not say how a person stayed involved.

Limitations

Prerequisites include a configured Hermes Agent instance, GitHub CLI authentication, and a valid Telegram delivery channel. The workflow relies on the agent's ability to correctly parse file paths and correlate code changes with documentation, which may require prompt tuning for different repo structures. Source reliability is secondary, as it is a documentation guide rather than a case study with verified results.

Try it

Act as a DevOps engineer setting up a documentation drift detector. I need you to configure a Hermes Agent cron job for the repository [replaceable_repo_name]. Steps: 1. Create a weekly cron job scheduled for Monday at 9 AM. 2. The prompt must instruct the agent to use `gh pr list` to fetch merged PRs from the last 7 days. 3. The agent should check if changes in [replaceable_code_paths] (e.g., tools/*.py) are reflected in [replaceable_doc_paths] (e.g., docs/reference/*.md). 4. If gaps are found, output a summary of the PR number, changed files, and missing doc updates. If no gaps, output [SILENT]. 5. Configure delivery to [replaceable_telegram_channel]. Before applying this to the live repo, run a dry test on a sample PR history to verify the logic. Show me the test output and ask for confirmation before creating the actual cron job. Ensure the GitHub CLI is authenticated and the Telegram bot is connected.

More cases · Software & development

• Update a code base with Copilot chat and agent mode
• Check code against user intent with review agents and tests
• Build a budgeting app from a single prompt
• Build a mental models framework with a multi-agent dev team
• Build a instant-opening markdown viewer for macOS