Index of every page on this site: llms.txt
All skills
cursor avatar

/weekly-review

@0b46ec3
by cursorcursor/plugins18k stars
1,933
Run it yourself

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

Use this Skill: https://skilld.dev/gh/cursor/plugins/weekly-review

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈29 tokens for metadata: the name and description. ≈190 when used: this file.

Description uses 1.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈117 characters, or 1.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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)

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill is structurally safe but processes external, untrusted content from git histories and diffs, presenting a potential surface for indirect prompt injection.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1/1 file flagged

Signed by skilld at 0b46ec3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 9 months ago

README badge

README badge for cursor/plugins/weekly-review