chore: import upstream snapshot with attribution
This commit is contained in:
wehub-resource-sync
@@ -0,0 +1,42 @@
|
||||
---
|
||||
name: nightly-changelog-loop
|
||||
description: Updates the changelog every night with user-relevant changes and notifies the team when it ships.
|
||||
category: operations
|
||||
interval: 24h
|
||||
stop-condition: The changelog reflects all merged, user-facing changes since the last entry and the team has been notified.
|
||||
components: [agent:documentation/changelog-generator, hook:automation/change-logger, hook:automation/slack-notifications]
|
||||
tags: [changelog, operations, release-notes, loop]
|
||||
---
|
||||
|
||||
# Nightly Changelog Loop
|
||||
|
||||
> **Loop Engineering** — a scheduled operations loop that turns the day's merges into a clean, user-facing changelog and announces it automatically.
|
||||
|
||||
## 🎯 Goal
|
||||
Each night, collect everything merged since the last entry, translate it into **user-relevant** changelog notes (not raw commits), and notify the team.
|
||||
|
||||
## ⏱️ Schedule
|
||||
Suggested interval: `24h` (run overnight).
|
||||
|
||||
## ▶️ Run it
|
||||
```
|
||||
/loop 24h "Gather all changes merged since the last changelog entry. Write clear, user-facing release notes grouped by Added/Changed/Fixed. Update the changelog file, commit it, and post a summary to the team channel. Skip internal-only changes."
|
||||
```
|
||||
|
||||
## 🔁 Iteration steps
|
||||
1. **Perceive** — read merges since the last changelog entry via `change-logger`.
|
||||
2. **Reason** — filter to user-facing changes; group as Added / Changed / Fixed.
|
||||
3. **Plan** — draft concise, human-readable notes.
|
||||
4. **Act** — update the changelog with `changelog-generator` and commit.
|
||||
5. **Observe** — post the summary through `slack-notifications`; confirm delivery.
|
||||
|
||||
## 🛑 Stopping condition
|
||||
Changelog covers all user-facing changes since the last entry and the team notification was sent.
|
||||
|
||||
## 🧩 Referenced components
|
||||
- `agent:documentation/changelog-generator` — writes the release notes.
|
||||
- `hook:automation/change-logger` — captures what changed.
|
||||
- `hook:automation/slack-notifications` — announces the update.
|
||||
|
||||
## 💡 Example
|
||||
Overnight the loop turns 14 merged PRs into 5 user-facing bullet points, commits `docs: changelog 2026-06-20`, and posts the summary to `#releases`.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: overnight-pr-routine-loop
|
||||
description: A nightly routine that watches your open PRs, auto-fixes build failures, answers review comments in a fresh worktree, and rebases stale branches while you sleep.
|
||||
category: operations
|
||||
interval: daily
|
||||
stop-condition: Every fixable PR is green and updated; anything ambiguous is left flagged for human review.
|
||||
components: [command:git-workflow/worktree-init, command:git-workflow/create-pr, agent:git/git-workflow-manager, hook:automation/slack-notifications]
|
||||
tags: [schedule, pull-requests, automation, loop]
|
||||
---
|
||||
|
||||
# Overnight PR Routine
|
||||
|
||||
> **Loop Engineering** — the `/schedule` verb runs a routine *while you are gone*. This is the "I don't write code, I write loops, and they write the code while I sleep" pattern: a scheduled routine that lands the fixable PRs overnight.
|
||||
|
||||
## 🎯 Goal
|
||||
Each night, work the open-PR queue: auto-fix build failures, answer review comments in an isolated worktree, rebase stale branches — and leave anything ambiguous for a human in the morning.
|
||||
|
||||
## ⏱️ Schedule
|
||||
Trigger: `daily` (overnight routine, runs while your laptop is closed).
|
||||
|
||||
## ▶️ Run it
|
||||
```
|
||||
/schedule every night, watch my open PRs. For each: auto-fix build failures, answer review comments in a fresh worktree, and rebase what is stale. Leave anything ambiguous or product-sensitive for me. Keep state in git so a crash loses nothing. Post a morning summary.
|
||||
```
|
||||
|
||||
## 🔁 Iteration steps
|
||||
1. **Perceive** — list open PRs and their CI/review state.
|
||||
2. **Isolate** — spin a fresh worktree per PR with `/worktree-init` (no cross-contamination).
|
||||
3. **Act** — `git-workflow-manager` fixes build failures, addresses review comments, rebases stale branches.
|
||||
4. **Verify** — re-run CI; push only when green; ambiguous items are flagged, never guessed.
|
||||
5. **Report** — post a morning summary via `slack-notifications`; update each PR with `/create-pr`.
|
||||
|
||||
## 🛑 Stopping condition
|
||||
Every fixable PR is green and updated; ambiguous/product-sensitive items are flagged for human review (not auto-merged).
|
||||
|
||||
## 💰 Budget & guardrails
|
||||
A nightly spend ceiling; never auto-merges; isolated worktrees so parallel fixes don't collide; state in git so a crash is recoverable.
|
||||
|
||||
## 🧩 Referenced components
|
||||
- `command:git-workflow/worktree-init` — isolated workspace per PR.
|
||||
- `command:git-workflow/create-pr` — updates/opens PRs.
|
||||
- `agent:git/git-workflow-manager` — safe rebases, fixes and comment replies.
|
||||
- `hook:automation/slack-notifications` — the morning summary.
|
||||
|
||||
## 💡 Example
|
||||
You wake up to three PRs rebased and green, two review comments answered with commits, and one PR flagged "needs a product decision" — exactly the one you should look at.
|
||||
Reference in New Issue
Block a user