skills.rest
jfmyers9
jfmyers9COMMUNITY
Explore all skills by this author →
WebsiteGitHub

report

Generate post-implementation execution reports summarizing commits and file changes.

8|Updated Jan 24, 2026
Search Tags:#automation#git#planning#diff#report#software
One-click install
npx skills add https://github.com/jfmyers9/agent --skill report-jfmyers9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: report
Source: https://github.com/jfmyers9/agent/tree/main/skills/report
Command: npx skills add https://github.com/jfmyers9/agent --skill report-jfmyers9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-implementation execution report summarizing commits, files changed, and plan-vs-reality. Triggers: 'report', 'execution report', 'what was built'.

Core Features & Use Cases

  • Derive project context and branch information from the repository.
  • Detect trunk/main and current branch, then compute diffs and file changes.
  • Generate and store a structured post-implementation report, optionally linking to a source plan.

Quick Start

Ask the AI to generate a post-implementation execution report for the current branch, including commits, changed files, and plan-vs-reality.

Frequently Asked Questions about report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically generate a post-implementation execution report for my Git branch?▼

An execution report is auto-generated by deriving project context from your repository, computing diffs between the current and trunk branches, and summarizing commits, changed files, and plan alignment. Triggering the 'report' command compiles this data into a structured narrative and metrics.

What is a post-implementation execution report and what does it summarize?▼

A post-implementation execution report is a document summarizing Git commits, file changes, and plan-versus-reality alignment. It compiles repository diffs and optional plan data to produce a comprehensive narrative and structured metrics detailing what was built on a branch.

Can I generate execution reports for merged changes in pull requests or releases?▼

Yes, execution reports can be generated for merged changes in pull requests or releases. The tool processes repository history and diffs for a specified override branch or merged changes, compiling commits and file changes into a structured summary.

Do I need to provide a project plan to generate a plan-vs-reality execution report?▼

Providing a source plan is optional when generating an execution report. The tool can compile a comprehensive narrative and structured metrics from repository history and diffs alone, but linking optional plan data enables the plan-versus-reality alignment summary.

What's the best way to summarize file changes and commits across a feature branch?▼

The best way to summarize file changes is to use an automated execution report tool that detects your trunk and current branches, computes the diffs, and compiles the commits and changed files into a structured post-implementation summary.

Related Skills

Explore More Software Engineering Skills→
Nathan13888Nathan13888
5

wtf

Summarize current git branch commits and diffs relative to trunk.

Community
Intermediate
89jobrien89jobrien
4

agile-ceremonies

Structure Agile standups, retrospectives, and sprint tracking with action items.

Community
Intermediate
awinogradovawinogradov
5

run

Automate development workflows from planning through pull request monitoring.

Community
Advanced
linenoizelinenoize
1

git

Generate conventional git commits, branch names, and pull request descriptions.

Community
Advanced