skills.rest
deveshkumars
deveshkumarsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Parse commits, PRs, and code quality signals into a weekly retro report.

Updated Mar 28, 2026
Search Tags:#automation#git#analysis#metrics#engineering#team#retro
One-click install
npx skills add https://github.com/deveshkumars/Intentra --skill retro-deveshkumars
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/deveshkumars/Intentra/tree/main/retro
Command: npx skills add https://github.com/deveshkumars/Intentra --skill retro-deveshkumars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives that analyze commit history, work patterns, and code quality metrics to surface team-wide insights and growth opportunities.

Core Features & Use Cases

  • Team-aware per-person praise and growth notes
  • Persistent history and trend tracking across sprints
  • Automated generation of actionable retrospectives for planning and review

Quick Start

Invoke the retro skill to generate the weekly retrospective for the current window.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate weekly retrospectives using git commit and PR data?▼

Automated weekly retrospectives parse git commits, pull requests, and code quality signals to produce a structured report covering per-person contributions, praise, and improvement opportunities for sprint planning and review.

What is a team-aware engineering retrospective and how does it surface growth opportunities?▼

Team-aware engineering retrospectives analyze work patterns and code quality metrics to surface team-wide insights, persistent history tracking, and actionable growth notes tailored to individual developers across sprints.

Can I generate retrospective reports across multiple projects and sprints?▼

Cross-project retrospective reports apply to weekly sprints and cross-project contexts, parsing engineering activity to surface deterministic per-person contributions and trend tracking across persistent sprint history.

What data sources are needed to analyze engineering activity for retrospective reports?▼

Engineering activity analysis requires deterministic inputs from git data, local telemetry, and gstack analytics to parse commits, PRs, and code quality signals for structured retrospective outputs.

Does the weekly retro analysis support integration with local telemetry and gstack analytics?▼

Weekly retro analysis integrates with local telemetry and gstack analytics, extracting deterministic inputs from git data to generate structured team-wide insights and actionable planning reports.

What are the limitations of automating sprint retrospectives from code metrics alone?▼

Automated sprint retrospectives from code metrics provide deterministic inputs from git data and telemetry but may not capture subjective team dynamics or qualitative feedback not reflected in commit and PR history.

Related Skills

Explore More Software Engineering Skills→
2460124601

retro

Generate weekly or cross-project engineering retrospectives from git history and contributor activity.

Community
Advanced
serejarisserejaris
215

cc-analytics

Analyze Claude Code history and Git data into weekly HTML reports.

Community
Intermediate
ericdahl-devericdahl-dev

gstack-openclaw-retro

Generate weekly engineering retrospectives from git commit history and code quality metrics.

Official
Advanced
shekerkammashekerkamma

retro

Analyze git commit history and code quality metrics to generate weekly engineering retrospective reports.

Community
Advanced