agentleFS
Sign inStart free
jholhewresjholhewres/devclaw-skills/skills/sprint-report/SKILL.md

sprint-report

Skill4 starsChanged 9 months agoMITView on GitHub

Generate sprint reports from git + issue tracker

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use bash (git + gh/jira CLI) to generate sprint reports.

    line 7
  2. Distinctive:

    Use memory_save to track velocity history

    line 35

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

Sprint Report

Use bash (git + gh/jira CLI) to generate sprint reports.

Collect Sprint Data

# Commits in sprint period
git log --since="2 weeks ago" --pretty=format:"%h %s (%an)" --no-merges | head -50
git shortlog --since="2 weeks ago" -sn

# PRs merged in sprint
gh pr list -R OWNER/REPO --state merged --search "merged:>=$(date -d '2 weeks ago' +%Y-%m-%d)" --json number,title,author --limit 50

# Issues closed in sprint
gh issue list -R OWNER/REPO --state closed --search "closed:>=$(date -d '2 weeks ago' +%Y-%m-%d)" --json number,title,labels --limit 50

# Open issues (carry-over)
gh issue list -R OWNER/REPO --state open --label "sprint-current" --json number,title,assignees --limit 30

Report Sections

  • Velocity: issues completed vs planned
  • Completed: features, fixes, improvements
  • Carry-over: unfinished items
  • Blockers: items that were blocked
  • Metrics: PRs merged, commits, contributors

Tips

  • Compare with previous sprint for trends
  • Highlight scope changes (added/removed mid-sprint)
  • Use memory_save to track velocity history

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