AGENT SKILL

weekly-review

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

License 许可
MIT
最近更新
2026-10-26
Stars
★ 0
Forks
0

01 前言 Front Matter

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

03 SKILL.md 正文

OpenAI runtime contract

Read the adapter contract before this workflow. It maps provider selection, agent calls, loops, persistent state, history, verification, and authorization. That contract supersedes Cursor-specific execution syntax and unverified model fallbacks below; the engineering steps remain required. Use native tools in the current host by default. Cloud uses its available OpenAI models. No remote laptop connection, server URL or MCP setup is permitted. Optional local CLI adapters require explicit environment-local selection. Do not claim cross-provider diversity for OpenAI-only review.

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)

04 同仓库更多 Skills

noodlemind
noodlemind/pstack-plugin

why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

★ 0
noodlemind
noodlemind/pstack-plugin

unslop

Cut AI tells from any writing. Must always apply.

★ 0
noodlemind
noodlemind/pstack-plugin

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

★ 0
noodlemind
noodlemind/pstack-plugin

technical-writing

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

★ 0
noodlemind
noodlemind/pstack-plugin

teach

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

★ 0
noodlemind
noodlemind/pstack-plugin

tdd

Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.

★ 0