SkillsAdd

flpbalada/fb-skills

explain-yesterday-changes

Explain changes made yesterday as a simple list. Use when user asks what changed yesterday, what was implemented yesterday, or needs a non-technical change summary from recent git work.

First seen Jul 14, 2026

Installation

$ npx skills add flpbalada/fb-skills --skill explain-yesterday-changes
View on skills.sh ↗ GitHub repository ↗

Also in this package

Other skills from flpbalada/fb-skills · top by installs.

npx skills add flpbalada/fb-skills
progressive-disclosure 35 discuss-task 25 to-prd 22 project-structure 20 code-simplifier 18 code-architecture-tailwind-v4-best-practices 18 discuss-code 17 five-whys 17 react-useeffect-avoid 17 typescript-advanced-types 16

Browse all from flpbalada/fb-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 7
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,888 B
  • docs SUMMARY.md 218 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 4 installs

SKILL.md

Explain Yesterday Changes

Summarize yesterday's work.

Goal

Return a simple list of what changed or was implemented. Avoid developer-only details.

Flow

  1. Verify current directory is a git repository.
  2. If today is Monday, ask the user whether to use Friday instead of yesterday.
  3. Inspect commits from the target day using local git history.
  4. If commits are missing or unclear, inspect diffs for files changed on the target day when available.
  5. Group related changes into user-visible outcomes.
  6. Translate technical changes into editor/admin language.
  7. Mention uncertainty when git history cannot prove the change.

Commands

git rev-parse --git-dir
git log --since="yesterday 00:00" --until="today 00:00" --stat --oneline
git log --since="yesterday 00:00" --until="today 00:00" --patch
git log --since="last friday 00:00" --until="last saturday 00:00" --stat --oneline
git log --since="last friday 00:00" --until="last saturday 00:00" --patch

Rules

  • Keep output short.
  • Use plain language.
  • Focus on screens, content, settings, workflows, permissions, publishing, data, and admin actions.
  • Do not list internal refactors, dependency bumps, linting, or formatting unless they changed editor/admin behavior.
  • Do not invent intent beyond commits or diffs.
  • If today is Monday, do not inspect Sunday by default; ask first whether the user means Friday.
  • If there were no commits on the target day, say no committed changes found.

Output

Use EXAMPLES.md as style reference.

- [Changed or implemented editor/admin-facing outcome]
- [Changed or implemented editor/admin-facing outcome]