agentleFS
Sign inStart free
odytriceodytrice/metaskills/skills/weekly-review/SKILL.md

weekly-review

Skill1 starsChanged 14 days agoMITView on GitHub

Aggregate engineering activity into Docs/status/. Use for a weekly review, status update, or progress report.

95 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quarterly-review, daily-plan and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Phoenixrr2113Skill

    quarterly-review

    Quarterly review — strategic look at the last 3 months. Career trajectory, project health, life balance, big decisions ahead. Runs 1st of Jan/Apr/Jul/Oct.

    Also in 3 projects that use this

  • steptianSkill

    daily-plan

    每日待办计划与日程管理。触发词：'今天要做'、'今日计划'、'今日待办'、'今天安排'、'安排一下'、'加个任务'、'记个任务'、'今日复盘'、'今日回顾'、'今天总结'、'本周计划'、'周总结'、'开始工作'、'上班了'、'完成了'、'加个日程'、'记个日程'、'改一下时间'、'日程调整'、'面试'、'开会'、'约了'。支持四象限优先级、时段分配、固定日程管理、智能时间估算、每日/每周复盘。当用户提到有明确时间的安排（如'下午两点面试'、'10点开会'），自动识别为日程并写入日程表。

    Also in 3 projects that use this

  • seedprodSkill

    daily-brief

    Send a morning briefing via Telegram with weather, news, and a motivational quote. Designed to run via launchd for automated daily delivery.

    Also in 5 projects that use this

  • claude-office-skillsSkill

    meeting-notes

    >

    Also in 8 projects that use this

  • Phoenixrr2113Skill

    morning-brief

    Full morning brief — calendar, email, meeting prep, execute actionable items, create follow-up tasks. Runs at 8:03 AM or when Randy asks for a morning update.

    Also in 4 projects that use this

  • zephyrwang6Skill

    daily-review

    每日工作回顾与洞察分析，对用户前一天的对话历史和使用数据进行总结与建议

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Weekly Review

Deterministic aggregation; when delegating, prefer a cost-efficient model with Docs/ writes and read-only gh/git.

From AGENTS.md: § Project Overview (product/themes), § Repositories (app/deployment repos), § Project Board. Explicit board: none: skip counts per issue-plan. Missing/incomplete board facts or required sections: name them and stop.

Process

  1. Range: last 7 days unless the user gives one.

  2. Gather:

    gh api --paginate 'repos/<owner>/<repo>/issues?state=all&per_page=100'
gh api --paginate 'repos/<owner>/<repo>/pulls?state=all&per_page=100'
gh api --paginate 'repos/<owner>/<repo>/actions/runs?per_page=100'
git log --since="7 days ago" --oneline --decorate

    Use documented app repo; repeat runs only for documented deployment repo. Exclude pull_request issue entries. Fully paginate before date filtering; retain open items for backlog metrics. Board counts: issue-plan § Board Status Transitions' complete read, consuming-repo Issue filter, retained URL/repo identity. Samples are not totals; unavailable/incomplete data is unknown, never zero/complete. Read existing Docs/ and Docs/status/. Local validation only if requested or cheap and relevant.

  3. Themes: derive from labels/milestones, § Project Overview areas, recurring commit/path subsystems. Include active security/auth, deployment/CI, documentation themes.
  4. Critical items: highest-priority open issues, blockers, stale PRs, failed app/deployment CI/CD, new data-integrity/auth risks.

  5. Write Docs/status/YYYY-MM-DD-weekly-review.md (create the directory if needed):

    # Developer Team Status Update - YYYY-MM-DD
## Executive Summary
## Completed
## In Review
## In Progress
## Critical Items
## Metrics
## Next Week

Metrics: open issues by priority/label; top blockers opened/closed; merged/open PRs; observed-only build/test status; latest pipeline per repo; defined board Status counts; milestone/ship-list status if defined in AGENTS.md/Docs/.

Link issues/PRs; mark stale docs historical. No secrets/token values.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free