agentleFS
Sign inStart free
xsovad06xsovad06/sova/.agents/skills/sova-standup/SKILL.md

sova-standup

Skill3 starsChanged 5 days agoApache-2.0View on GitHub

Daily standup summary (git state, open PRs, GitHub Issues, and suggested focus).

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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. Distinctive:

    If on a feature branch: git rev-list --count main..HEAD

    line 18
  2. Distinctive:

    If the project uses GitHub Projects:

    line 32
  3. Very specific:

    Want to pick up a new task?: Run the sova-find-task skill

    line 45
  4. Very specific:

    Ready to work on something?: Run the sova-develop-full skill <ISSUE_NUMBER>

    line 46
  5. Distinctive:

    NEVER use emojis in any output

    line 50

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

Daily Standup

Generate a quick daily context dump.

Instructions

  1. Git state:
    git branch --show-current
git status --short
git log --oneline -5
    If on a feature branch: git rev-list --count main..HEAD
  2. Open PRs:
    gh pr list --author @me --state open
    For each: number, title, check status, review state. Flag PRs with failing checks.
  3. Assigned issues:
    gh issue list --assignee @me --state open --json number,title,labels,milestone
    Group by status labels (e.g., in-progress, backlog, blocked). If the project uses GitHub Projects:
    gh project item-list --owner <OWNER> --format json 2>/dev/null || true
  4. Present summary:
    • Working on: current branch + uncommitted changes
    • Open PRs: list with CI/review status
    • Issue queue: grouped by status/priority
    • Suggested focus: what to work on based on priority and blockers

Cross-References

  • Want to pick up a new task? Run the sova-find-task skill
  • Ready to work on something? Run the sova-develop-full skill <ISSUE_NUMBER>

Rules

  • NEVER use emojis in any output

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