agentleFS
Sign inStart free
lucastosettolucastosetto/dev-skills/skills/standup/SKILL.md

standup

Skill0 starsChanged 25 days agoMITView on GitHub

Prepare what to say at the daily standup: everything you did since the last daily (commits, your PRs and their state, PR reviews you gave, ticket activity, Claude Code sessions, investigations and specs, Slack threads), what's planned today, and blockers, as a short bullet message readable in under 30 seconds. Use on "standup", "daily update", "what did I do since yesterday", "prepare my daily", "/standup".

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 7 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

  • 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

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Follow ../../shared/policy.md.

    line 15
  2. Very specific:

    Start: the previous business day's daily (business days as defined in the sprint skill), using daily_time from ### standup in defaults.md …

    line 18
  3. Very specific:

    All repos with a profile in ~/.dev-skills/profiles/ (each profile's Repo: path), plus the current repo.

    line 23
  4. Very specific:

    Leave out empty sections. One line per item.

    line 61

“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

Follow ../../shared/policy.md. Reads only.

1. Window

  • Start: the previous business day's daily (business days as defined in the sprint skill), using daily_time from ### standup in defaults.md or the current profile (default 10:00 local). Monday reaches back to Friday's daily; a holiday is skipped the same way. since <...> overrides.
  • End: now.

2. Repos and boards

All repos with a profile in ~/.dev-skills/profiles/ (each profile's Repo: path), plus the current repo. Their trackers and PR hosts from the profiles.

3. Collect (only items by you, in the window)

SourceHow
Commitsper repo: git log --all --author="$(git config user.email)" --since=<start> --format="%h %ad %s %D" (also try user.name)
Your PRsopened, pushed to, merged, approved, changes requested (pr-hosts.md)
Reviews you gavePRs you reviewed or commented on, with your verdict
Ticketsones you moved, commented on, or created (trackers.md)
Claude Code sessions~/.claude/projects/*/*.jsonl modified in the window: read the user prompts and final assistant replies of each session in the window; extract work that has no git trace (investigations, reviews not posted, research, plans). Summarize only.
dev-skills workfiles under ~/.dev-skills/work/ modified in the window (context.md, spec.md, investigation.md, ...)
Slackif connected: threads you replied in (e.g. support answers)
Plantoday's tickets from the current sprint plan (dev-skills:sprint file; on a non-business day, the next business day)

4. Merge

One line per ticket or PR, combining every source ("PROJ-123: fixed and opened PR, answered the support thread"). Drop noise: base-branch merges, staging redeploys, revert-and-redo churn, WIP commits. Name tickets by key plus a few words of what the work was, not branch names.

5. Blockers (found automatically)

  • Your PRs waiting for review longer than review_wait (default 1 workday).
  • Questions to product/manager still unanswered (from context.md unknowns sent earlier).
  • Tickets marked blocked, or failing CI on your PRs.

Output

Done:
- PROJ-123 PR opened — <few words>
- Investigated <issue>: <cause in a clause>
- Reviewed: <repo>#45, <repo>#51
In progress:
- PROJ-130 addressing review comments
Today:
- PROJ-131, PROJ-134
Blockers:
- PROJ-128 PR waiting for review 2 days

Leave out empty sections. One line per item; whole message readable in under 30 seconds. Output to chat, or also to a file when output: file <path pattern> is set under ### standup ({date} placeholder allowed; the file must be outside any repo).

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