skills.rest
howdeploy
howdeployCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze commit history and work patterns to generate weekly engineering retrospectives.

15|1|Updated Apr 4, 2026
Search Tags:#retrospective#engineering#code-quality#sprint#team#commit-history#retro
One-click install
npx skills add https://github.com/howdeploy/NekoFree --skill retro-howdeploy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/howdeploy/NekoFree/tree/main/skills/retro
Command: npx skills add https://github.com/howdeploy/NekoFree --skill retro-howdeploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that analyze commit history, work patterns, and code quality signals to surface actionable improvements for the team.

Core Features & Use Cases

  • Per-person contribution breakdowns across sprints with praise and growth areas.
  • Persistent history and trend tracking to reveal patterns in team performance over time.
  • Team-aware summaries that guide process improvements and future sprint planning.

Quick Start

Tell me to run a weekly retro for this sprint.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a sprint retrospective from commit history?▼

Generate a sprint retrospective by analyzing commit history and work patterns to surface actionable team improvements. The retrospective breaks down per-person contributions, highlighting praise and growth areas to guide future sprint planning.

What is an engineering retrospective and how does it track team performance?▼

An engineering retrospective is a weekly review analyzing code quality signals to improve team workflows. It tracks performance trends over time using persistent history storage, revealing long-term patterns in team contributions.

Can I use this retrospective tool for individual sprint contribution breakdowns?▼

Yes, you can use this retrospective for individual sprint contribution breakdowns. It provides team-aware summaries that detail each person's work, identifying specific praise and growth areas based on their commit history.

Does the weekly retro support persistent history for long-term trend tracking?▼

Yes, the weekly retro supports persistent history for long-term trend tracking. It stores historical retrospective data to reveal patterns in team performance over time, enabling continuous process improvements across sprints.

What is the best way to run a team-aware engineering retro?▼

The best way to run a team-aware engineering retro is to analyze commit history and code quality signals together. This approach generates summaries that guide process improvements while incorporating new data sources as needed.

Related Skills

Explore More Software Engineering Skills→
esopianesopian
2

retro

Analyze git commit history and code metrics to generate team retrospectives.

Community
Intermediate
MichaelSolatiMichaelSolati

retrospective

Compile and analyze sprint retrospective data from project artifacts into structured reports.

Community
Advanced
asgarovfasgarovf
23

code-review

Analyze pull requests for security vulnerabilities and SOLID principles.

Community
Advanced
mahg-esmahg-es
3

velocity

Calculate team velocity metrics from sprint history and generate a velocity report.

Official
Intermediate