AGENT SKILL

status-report

Builds a status report (weekly or for a period) by combining git history, the task tracker and hub memory; returns done / in progress / blockers / next steps. Use when asked for a status report, a weekly, "what did I do this week", a standup summary or an update for a manager.

License 许可
MIT
所属仓库
ngentile92/mnemos
最近更新
2026-11-02
Stars
★ 4
Forks
1

01 前言 Front Matter

name
status-report
metadata
{ "version": "1", "hub-owner": "shared" }
description
Builds a status report (weekly or for a period) by combining git history, the task tracker and hub memory; returns done / in progress / blockers / next steps. Use when asked for a status report, a weekly, "what did I do this week", a standup summary or an update for a manager.

03 SKILL.md 正文

Status report

1. Scope

Confirm the period (default: last 7 days, Monday to today), the context (hub_whoami) and the audience (manager, team, yourself). Write in the language the audience uses.

2. Sources (in this order)

  1. Memory: memory_search "progress / decisions / blockers <period>"; in contexts with projects, filter by project.
  2. Git (if you have a shell on the user's machine): the user's repos for this context. Don't assume a folder: use the location memory has for them, otherwise ask, and set ROOT to it.
    ROOT="<folder that holds the repos>"   # e.g. where the user keeps their clones
    for d in "$ROOT"/*/; do
      [ -d "$d/.git" ] || continue
      out=$(git -C "$d" log --all --since="7 days ago" --author="$(git config user.email)" \
            --no-merges --format='%cs %h %s')
      [ -n "$out" ] && printf '## %s\n%s\n' "$(basename "$d")" "$out"
    done
    
    With gh, add PRs: gh pr list --author @me --state all --search "updated:>=YYYY-MM-DD".
  3. Task tracker (Jira, Linear, ClickUp, GitHub Issues... if a connector is available): tasks assigned to the user and updated in the period: closed, in progress, overdue.
  4. If a source is unavailable, say so in the report; don't fill it in from memory.

3. Format

# Status <period> — <context>
**TL;DR:** 2-3 lines with what matters most.

## Done
- <outcome, not activity> (repo/PR or task)
## In progress
- <what> — <% or next milestone> — ETA
## Blockers / risks
- <blocker> — what is needed and from whom
## Next steps
- …
  • Group commits by theme/feature; don't list individual commits. Outcome > activity ("ingestion is stable for the pilot", not "commits in repo X").
  • At most ~15 bullets. Link PRs and tasks when they exist.
  • Anything without evidence (no commit, task or note) goes in as "to confirm".

4. Wrap-up

  • Don't send it by chat or email until the user approves the final text.
  • memory_save a short note: "Status <date>: done X, in progress Y, blockers Z" (right context; project where required).

04 同仓库更多 Skills

ngentile92
ngentile92/mnemos

incident-postmortem

Writes a blameless incident postmortem (timeline, impact, root cause, contributing factors, action items) from logs, chat history or notes. Use after an outage, a failed deploy or a production bug, or when asked for an "incident report" or "postmortem".

★ 4
ngentile92
ngentile92/mnemos

release-notes

Writes user-facing release notes and a changelog entry from merged PRs or commits since the last release. Use when asked for "release notes", a "changelog" or "what changed since vX".

★ 4
ngentile92
ngentile92/mnemos

technical-docs

Writes technical documentation, specs and design docs (context, goals, ADR-style decisions, mermaid diagrams, rollout plan) and suggests where to store them. Use when asked to "document this", for a design doc, a spec, an ADR, a technical proposal or an architecture README.

★ 4
ngentile92
ngentile92/mnemos

review-pr

Reviews a pull request with a fixed checklist (correctness, security, tests, readability) and returns prioritized findings. Use when asked to review a PR, a diff or a code change.

★ 4
ngentile92
ngentile92/mnemos

memory-capture

Decides what is worth remembering from the conversation and saves it as short, self-contained notes with [[links]] to people, companies and projects. Use when the user says "remember this", "save this", "note that", or at the end of a session with decisions worth keeping.

★ 4
ngentile92
ngentile92/mnemos

meeting-notes

Turns a meeting transcript or rough notes into a summary with decisions, action items (owner + date) and open questions, and saves the durable parts to memory. Use when the user pastes a transcript, call notes or says "summarise this meeting".

★ 4