Weekly review

Skill broomva/skills/skills/cadence/weekly-review

Broomva agent-skills monorepo — 48 Tier-2 skills compatible with Claude Code, Codex, Cursor, Gemini CLI, Goose, Copilot. Layout follows anthropics/skills (agentskills.io spec). Install: npx skills add broomva/skills --skill <name>.

Install

npx -y skills add broomva/skills --skill weekly-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Scans the vault for updates from the past week, surfaces what changed, and flags what needs attention. Produces a structured weekly review. Use when the user says "weekly review", "week in review", "what happened this week", "weekly summary", "end of week review", or at the end of a work week.

SKILL.md

3.0 KB, as published. Nobody here has run it

Weekly Review

Scan the week. Surface what matters. Plan what's next.

Workflow

Scan vault changes — Find all files in ~/broomva-vault/ modified in the last 7 days:
- New notes created
- Existing notes modified (check git or file timestamps)
- Group by folder/project
Scan git activity — Run across all repos under ~/broomva/:
- git log --since="7 days ago" --oneline --stat
- Count commits per repo
- Identify PRs merged, branches created
Extract completed items — Find tasks marked done this week:
- - [x] items with recent modification dates
- Completed items in project trackers
Find open items — Surface things that need attention:
- Overdue tasks (- [ ] with past dates)
- Stale PRs or branches
- Notes tagged with urgency markers
- Items promised in last week's review that aren't done
Identify themes — What patterns emerge from the week's activity:
- What projects got the most attention?
- Any new projects or ideas that emerged?
- Any projects that went silent?
Generate next week's priorities — Based on:
- Unfinished items from this week
- Upcoming deadlines
- Momentum (what's hot, what's stalled)

Output Format

## Weekly Review — [Week of YYYY-MM-DD]

### Week at a Glance
- **Commits**: [N] across [M] repos
- **Notes created**: [N]
- **Notes modified**: [N]
- **Tasks completed**: [N]
- **Tasks still open**: [N]

### What Got Done
- [Completed item] — [[Project]]
- [Completed item] — [[Project]]

### What's Still Open
**Overdue**
- [ ] [item] — due [date] — [[Project]]

**In Progress**
- [ ] [item] — [[Project]]

**Stalled** (no activity this week)
- [ ] [item] — last touched [date] — [[Project]]

### Project Activity
| Project | Commits | Notes | Status |
|---------|---------|-------|--------|
| [name] | N | N | Active / Quiet / New |

### Themes & Observations
- [What dominated the week]
- [Any surprising patterns]
- [Things to watch]

### Next Week's Priorities
1. [Priority] — why: [reason]
2. [Priority] — why: [reason]
3. [Priority] — why: [reason]

### Carry-Forward
- [ ] [Item from this week that must continue]

Vault Integration

Save to: ~/broomva-vault/reviews/weekly-review-[YYYY-MM-DD].md
Link back to project notes referenced
If prior weekly reviews exist, reference the most recent one for continuity

Behavior

Be factual about what happened — don't editorialize
Highlight things that slipped without judgment
The "next week's priorities" should emerge from the data, not be invented
If the vault is sparse, focus on git activity
Keep the whole review scannable in under 3 minutes