Skip to content
Back to skills

Weekly Review

ASecurity

Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work

  • 8 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 6, 2026
code-qualitygorailsgit

Works with

  • cursor

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 6, 2026

npx -y skills add v1truv1us/ai-eng-system --skill weekly-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Weekly Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Weekly Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/v1truv1us-weekly-review-731f911e/badge)](https://www.skillsdirectory.com/skills/v1truv1us-weekly-review-731f911e)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: weekly-review
description: Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work
metadata:
  category: user-invoked
  version: 1.0.0
  tags: cursor-import, cursor-team-kit
disable-model-invocation: true
---

Default output: return only the result, blockers, and required evidence. Omit preambles, process narration, repeated context, confidence scores, and follow-up offers. Use at most five bullets unless a required artifact or schema needs more.
# Weekly review

## Trigger

Need a weekly recap of shipped work for status updates, retros, or planning.

## Workflow

1. Determine the current git user email from repo config.
2. Collect authored commits from the last 7-10 days on the primary branch context.
3. Exclude merge commits.
4. Group meaningful changes into 2-5 concise bullets.
5. Add a short classification paragraph covering:
   - likely bug fixes
   - likely tech debt work
   - likely net-new functionality

## Guardrails

- Keep the recap short and executive-readable.
- Base claims only on commit history and diffs.
- If git email is missing, ask the user to set it before proceeding.

## Output

- 2-5 bullet weekly summary
- Brief classification paragraph (bugfix / tech debt / net-new)

Files in this skill

  • SKILL.md1.2 KB
  • evals/evals.json1.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…