agentleFS
Sign inStart free
oneafrikanoneafrikan/the-grid/skills/standup/SKILL.md

standup

Skill4 starsChanged 8 days agoMITView on GitHub

Generate a concise standup summary from recent git activity across repos. Use when the user says "standup", "what did I do yesterday" or "daily summary".

55 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close-day, meeting-prep 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.
  • vantageos-agencySkill

    close-day

    End-of-day routine: close tasks with their time, leave the repository and the disk clean, write the diary, harvest friction, and hand over to tomorrow. Use this skill whenever the user says "close day", "end of day", "fin de journée", "bonne nuit", "wrap up", "call it a day", "close session", "daily close", or mentions ending their work session -- even if they don't say "close-day" explicitly.

    Also in 3 projects that use this

  • OpenAISkill

    meeting-prep

    Use when creating Public Equity Investing meeting prep briefs. Do not use for private diligence, IB, FP&A, legal, or scheduling-only tasks.

    Also in 5 projects that use this

  • jasonmichaelbell78-creatorSkill

    todo

    Cross-session todo management with interactive menu, JSONL-backed persistence, and AI-powered context capture. Manages ideas, tasks, and insights that emerge during sessions so they survive across sessions. Independent of GSD.

    Also in 3 projects that use this

  • takleb3rrySkill

    kickoff

    Initialize a new project by analyzing source documents and generating requirements.md and design.md

    Also in 3 projects that use this

  • asterkinSkill

    adr

    Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.

    Also in 4 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run git log --oneline --since="yesterday" --author="$(git config user.email)" in the current repo (and any others the user mentions).

    line 13
  2. Distinctive:

    If no commits found, say so and ask if they want to check a different date range.

    line 36
  3. Distinctive:

    If the user says "today" instead of "yesterday", adjust the time range.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 51 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Standup

Generate a standup summary from recent git activity. Keep it short — a standup reader should be done in 30 seconds.

Process

  1. Run git log --oneline --since="yesterday" --author="$(git config user.email)" in the current repo (and any others the user mentions).
  2. Group commits by logical theme, not by repo or time.
  3. Identify any blockers mentioned in commit messages (TODO, FIXME, WIP, blocked).
  4. Output the summary in standup format below.

Output format

Yesterday
- [thing done]
- [thing done]

Today
- [what's next, inferred from WIP commits or ask the user]

Blockers
- [any, or "none"]

Rules

  • One line per item. No bullet nesting.
  • Drop commit hashes, branch names, and merge noise.
  • If no commits found, say so and ask if they want to check a different date range.
  • If the user says "today" instead of "yesterday", adjust the time range.

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