agentleFS
slashnote-appslashnote-app/claude-code-plugin/skills/note-standup/SKILL.md

note-standup

Skill1 starsChanged 9 months agoMITView on GitHub

Generate a daily standup summary from git activity, notes, and PRs

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 11 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    If found → save its id — will use mcp__slashnote__update_note in Step 2 instead of creating new

    line 31
  2. Distinctive:

    If not found → will create a new note in Step 2

    line 32
  3. Distinctive:

    Read notes with checkboxes to find:

    line 44
  4. Distinctive:

    Check note-loop note for current task

    line 48
  5. Distinctive:

    Check loop state file for blocked tasks

    line 49
  6. Distinctive:

    Create or update a green note (update if Step 0 found an existing one for today):

    line 53
  7. Distinctive:

    If no planned items → omit section

    line 99
  8. Distinctive:

    Omit entirely: if no blockers — don't show empty section

    line 105
  9. Very specific:

    When git is not available or --notes flag used:

    line 109
  10. Distinctive:

    No git/PR calls at all

    line 125
  11. Distinctive:

    If no commits → skip git items in "Done" (still show note completions)

    line 150
  12. Distinctive:

    If no in-progress → omit section or show "Clear — ready for new tasks"

    line 151
  13. Distinctive:

    If no blockers → omit "Blockers" entirely

    line 152

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

/note-standup — Daily Standup

Generate a standup report from git commits, SlashNote notes, and PR activity.

Usage

/note-standup                  # Default: since yesterday
/note-standup --week           # Weekly summary
/note-standup --notes          # Notes-only mode (no git required)

Behavior

Step 0: Find existing standup to update

  1. mcp__slashnote__search_notes with query "Standup"
  2. Among results, find one where preview starts with "Standup" AND createdAt is today's date
  3. If found → save its id — will use mcp__slashnote__update_note in Step 2 instead of creating new
  4. If not found → will create a new note in Step 2

Step 1: Collect data

Git + PR data (skip if --notes or not in a git repo):

echo "COMMITS:" && git log --oneline --since="yesterday" --author="$(git config user.name)" 2>/dev/null && echo "---FILES---" && git diff --stat HEAD~5 --shortstat 2>/dev/null && echo "---PRS---" && gh pr list --author="@me" --state=all --limit=5 --json title,state,updatedAt 2>/dev/null || echo "no-gh"

For --week: use --since="1 week ago" and HEAD~20

SlashNote data (always collected):

  1. mcp__slashnote__list_notes — get all notes
  2. Read notes with checkboxes to find:
    • Recently completed items (done checkboxes)
    • In-progress items
    • Bug notes (pink)
  3. Check note-loop note for current task
  4. Check loop state file for blocked tasks

Step 2: Generate standup

Create or update a green note (update if Step 0 found an existing one for today):

# Standup <date>
<N commits, M files changed, K PRs>

## Done
- <grouped commit summaries>
- <completed checkbox items>
- <merged PRs>

## In Progress
- <in-progress checkbox items>
- <open PRs>

## Today
- <unchecked note-loop/note-todo items — what's planned next>

## Blockers
- <blocked tasks>
- <recent bug notes>

Section Details

Metrics Line

Right below the title, one line of activity metrics:

  • 5 commits, 12 files changed, 2 PRs (git mode)
  • 3 tasks completed, 2 in progress (notes mode)
  • Omit if no meaningful metrics

"Done" Section

  • Group related commits by conventional commit prefix (see table below)
  • Include completed checkbox items from notes
  • Include merged PRs: PR: "Title" (merged)
  • Max 10 items — summarize if more

"In Progress" Section

  • In-progress checkboxes from notes
  • Open/draft PRs: PR: "Title" (open, N reviews)
  • Current note-loop task
  • Max 7 items

"Today" Section

  • Source from unchecked checkboxes in note-loop/note-todo notes
  • This is the plan, not history
  • If no planned items → omit section
  • Max 5 items

"Blockers" Section

  • Blocked tasks from loop state file
  • Recent bug notes (pink, created in last 24h)
  • Omit entirely if no blockers — don't show empty section

Non-Git Mode (--notes or no git repo)

When git is not available or --notes flag used:

# Standup <date>
<N tasks completed, M in progress>

## Done
- <completed checkbox items from notes>

## In Progress
- <in-progress items from notes>

## Today
- <unchecked items from note-loop/note-todo notes>
  • No git/PR calls at all
  • Works everywhere — not just in git repos

Commit Grouping

PrefixGroup Label
fix:, bugfix:Bug fixes
feat:, feature:Features
refactor:Refactoring
docs:Documentation
test:Tests
chore:, ci:Maintenance
No prefixGroup by modified area

Example: 3 commits with feat: prefix → single line: "Features: animated AI loader, heading placeholders, voice input"

Rules

  • One Bash call max for git+PR+files data (combined command)
  • Group related commits — never list individual commits raw
  • Concise: one line per item, no full commit messages
  • Skip merge commits and CI-related commits
  • Date: human-readable ("Feb 19, 2026")
  • PR activity: PR: "title" (merged/open/draft)
  • If no commits → skip git items in "Done" (still show note completions)
  • If no in-progress → omit section or show "Clear — ready for new tasks"
  • If no blockers → omit "Blockers" entirely
  • Max items per section: Done=10, In Progress=7, Today=5, Blockers=5

Examples

Git + Notes:

# Standup Feb 19, 2026
5 commits, 12 files changed, 2 PRs

## Done
- Features: animated AI loader, heading placeholders
- Bug fixes: removed debug Pro override, restored Pro gates
- PR: "Add voice input support" (merged)
- Completed plugin skills research

## In Progress
- Skills plugin deep dive (9/12 done)
- PR: "Refactor NoteStorage" (open, 2 reviews)

## Today
- Finish /note-standup improvements
- Start /note-wrapup deep dive
- Review open PR feedback

## Blockers
- Bug: race condition in WebSocket handler

Notes-only (--notes):

# Standup Feb 19, 2026
3 tasks completed, 2 in progress

## Done
- Improved /note auto-detection
- Created /note-context skill
- Improved /note-find search UX

## In Progress
- /note-standup deep dive
- Plugin integration tests

## Today
- Finish /note-wrapup improvements
- Start /note-context deep dive

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.