agentleFS
ek33450505ek33450505/claude-agent-team/skills/git-activity/SKILL.md

git-activity

Skill8 starsChanged 31 days agoMITView on GitHub

Scan project repositories for yesterday's git activity. Use when summarizing development progress for briefings, reports, standups, or when user asks "what did I work on yesterday" or "recent commits".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

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

    Run the following script:

    line 18
  2. Very specific:

    If no activity at all: *No commits yesterday*

    line 49

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

Git Activity

Scan known project directories for git commits since yesterday.

Project Directories

Sourced from ~/.claude/config.sh. Edit that file to add or remove projects.

Instructions

  1. Run the following script:
source ~/.claude/config.sh
for dir in "${PROJECTS[@]}"; do
  if [ -d "$dir/.git" ]; then
    count=$(git -C "$dir" log --since="yesterday" --oneline 2>/dev/null | wc -l | tr -d ' ')
    if [ "$count" -gt 0 ]; then
      remote=$(git -C "$dir" remote get-url origin 2>/dev/null || echo "local")
      if echo "$remote" | grep -q "bitbucket"; then
        host="Bitbucket"
      elif echo "$remote" | grep -q "github"; then
        host="GitHub"
      else
        host="local"
      fi
      echo "=== $(basename $dir) ($count commits) [$host] ==="
      git -C "$dir" log --since="yesterday" --oneline 2>/dev/null
    fi
  fi
done
  1. Return output as a markdown table (omit repos with 0 commits):
| Project | Host | Commits | Summary |
|---------|------|---------|---------|
| my-project | GitHub | 3 | feat: add chart, fix: tooltip, chore: deps |

If no activity at all: *No commits yesterday*

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.