skills.rest
derekhu0002
derekhu0002COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ai4pb-iteration-summary

Generate a conventional-commit summary of iteration changes and save it to debug/iteration-commit-message.md.

Updated Mar 1, 2026
Search Tags:#automation#git#commit#iteration#diff#summarize
One-click install
npx skills add https://github.com/derekhu0002/ai4pb-orchestrator --skill ai4pb-iteration-summary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai4pb-iteration-summary
Source: https://github.com/derekhu0002/ai4pb-orchestrator/tree/main/.opencode/skills/ai4pb-iteration-summary
Command: npx skills add https://github.com/derekhu0002/ai4pb-orchestrator --skill ai4pb-iteration-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of concise, standards-compliant Git commit messages that summarize all meaningful changes from the current iteration.

Core Features & Use Cases

  • Generates a subject and body for a commit that reflects features, fixes, refactors, and release-related changes.
  • Applies sprint-start boundaries, diff ranges, and classification rules to produce a structured message suitable for release notes.
  • Ensures persistence by saving the final message to debug/iteration-commit-message.md for audit and review.

Quick Start

Run the iteration summary tool to generate and save the commit message to debug/iteration-commit-message.md

Frequently Asked Questions about ai4pb-iteration-summary

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

FAQPage Schema
How do I automatically generate a git commit message for an iteration?▼

You can generate a conventional commit summary by identifying all meaningful changes from the iteration start to HEAD, classifying them into Feature, Fix, or Refactor categories, and saving the structured message to a markdown file.

How does a sprint-start tag change the way iteration changes are summarized?▼

A sprint-start tag defines the iteration boundary for summarizing changes. When the latest sprint-start tag exists, the tool includes staged, unstaged, and untracked changes up to HEAD; without it, only current changes are summarized.

How do I classify git diff changes into features and fixes for release notes?▼

Classifying git diff changes for release notes involves categorizing modifications into Feature, Fix, Refactor, Build/Release, or Drift/Unrelated groups to produce a structured conventional-commit message suitable for auditing.

Can I include untracked and unstaged changes in an automated commit summary?▼

Yes, you can include untracked and unstaged changes in the commit summary if a sprint-start tag is present to serve as the iteration boundary, otherwise the summary is generated using only current changes.

Where are generated iteration commit messages saved for audit and review?▼

Generated iteration commit messages are saved directly to the debug/iteration-commit-message.md file, ensuring the conventional-commit summary persists for later audit and review purposes.

Related Skills

Explore More Software Engineering Skills→
FrancisVargaFrancisVarga

changelog

Generate categorized release notes from git commits and sprint reports.

Community
Advanced
ctrsploitctrsploit
153

commit-message

Generate semantic Git commit messages from staged changes using Conventional Commits.

Official
Intermediate
jayteealaojayteealao

git-release-workflow

Automate git release operations by staging changes, creating a formatted commit, and tagging.

Community
Basic
mgoodman60mgoodman60

commit

Generate descriptive Git commit messages from repository changes with conventional formatting.

Community
Basic