skills.rest
sqfzy
sqfzyCOMMUNITY
Explore all skills by this author →
GitHub

report

Generate structured stakeholder reports from git history, artifacts, and code changes.

Updated Jul 5, 2025
Search Tags:#automation#communication#artifacts#report#git-history#stakeholders#data-backed
One-click install
npx skills add https://github.com/sqfzy/my_configs --skill report-sqfzy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: report
Source: https://github.com/sqfzy/my_configs/tree/main/claude/skills/report
Command: npx skills add https://github.com/sqfzy/my_configs --skill report-sqfzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of concise, decision-ready reports for stakeholders by pulling data from git history, .artifacts/, and code changes, reducing manual reporting effort and improving consistency.

Core Features & Use Cases

  • Automated data collection from git history, artifacts, and code changes to populate reports.
  • Conclusion-first, action-oriented structure that guides readers to decisions and next steps.
  • Configurable outputs, sources, and trigger conditions to fit team workflows.
  • Use Case: Generate a weekly executive summary for leadership, a project status update for a product review, or an incident report for a post-mortem review.

Quick Start

Ask me to generate a weekly status report for the executive team using the latest git history and artifacts.

Frequently Asked Questions about report

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

FAQPage Schema
How do I automate stakeholder report generation from git history and project artifacts?▼

Generate weekly or monthly stakeholder reports automatically by configuring the tool to extract data from git history, .artifacts/, and code changes. It structures outputs with conclusions first, guiding readers to decisions and next steps.

What is a conclusion-first stakeholder report and why use it for executive updates?▼

A conclusion-first stakeholder report states key findings and decisions upfront before detailing supporting data. This format guides readers to immediate decisions and next steps, making it ideal for executive updates and project status reviews.

Can I configure report sources and trigger conditions to fit my team's workflow?▼

Yes, you can configure output formats, data sources, and trigger conditions to fit team workflows. This allows you to generate weekly executive summaries, product review status updates, or incident post-mortem reports as needed.

What's the best way to create decision-ready reports from code changes and artifacts?▼

Create decision-ready reports by using an automated tool that extracts data from git history, .artifacts/, and code changes. It formats the information with a conclusion-first, action-oriented structure for stakeholders.

Does automated report generation work for both technical proposals and weekly status updates?▼

Yes, automated report generation supports both technical proposals and weekly or monthly status updates. It populates the reports with data-backed information from git history and artifacts for executives, managers, and post-mortem reviews.

Related Skills

Explore More Content & Communication Skills→
AIS-Commercial-Business-UnitAIS-Commercial-Business-Unit

ais.report.project

Generate detailed software project reports from pipeline status, team activity, and health indicators.

Official
Advanced
nimrodfishernimrodfisher
351

insight-synthesis

Summarize analysis findings into decision-oriented insights for executive stakeholders.

Community
Advanced
teambitteambit
18.5k

generate-release-notes

Generate release notes from commits and pull requests via GitHub API.

Official
Advanced
fabioc-alohafabioc-aloha
1

status-reporting

Generate stakeholder-friendly project status updates from technical progress.

Community
Intermediate