Generates weekly engineering retrospectives from git commit history and work pattern metrics.
npx skills add https://github.com/no-session/pstack --skill reflect-no-session
Please help me install this Agent Skill. Skill: reflect Source: https://github.com/no-session/pstack/tree/main/reflect Command: npx skills add https://github.com/no-session/pstack --skill reflect-no-session
.context/retros/ and compares current metrics against prior retros, plus week-over-week trends and shipping streaks. - Team & Solo Modes: Produces per-author leaderboards with praise and growth opportunities for teams, or deep personal analysis for solo repos; supports cross-project global retros. - Use Case: At the end of a work week, run the retro to see that your fix ratio hit 54%, your deep sessions dropped from 5 to 2, and your test coverage fell 19 points — then adjust next week's plan accordingly. ## Quick Start Ask the AI to run a weekly engineering retrospective over the last 7 days of git history and summarize shipping velocity, session patterns, and code quality trends.High-intent search queries and answers about installing and using this skill.
Run the retro command with a time window such as 7d, 14d, or 30d. It analyzes commits, LOC, sessions, hotspots, and test ratios from git log, then produces a metrics summary, per-author leaderboard, and trend comparison against prior retros.
It tracks commits, insertions and deletions, test LOC ratio, PR size distribution, detected work sessions, commit type breakdown (feat/fix/refactor), file hotspots, focus score, shipping streaks, and week-over-week trends for windows of 14 days or more.
Yes. Use the compare mode to contrast the current window with the prior same-length window. The skill also saves each retro as a JSON snapshot and automatically shows deltas in test ratio, sessions, LOC per hour, and fix ratio versus the last recorded retro.
Yes. When only one contributor is detected, it skips the team breakdown and runs a personal retro focused on your session patterns, peak hours, focus score, and biggest ship of the period.
Yes. The global mode runs a cross-project retro across all AI coding tools without requiring you to be inside a git repository. Pass an optional window like 14d to control the analysis period.
A fix ratio above 50% signals a ship-fast-fix-fast pattern that may indicate review gaps. The skill calls this out so you can add review or test coverage before defects compound.
tanveerriazEnforces working-branch-only commits, conventional messages, and approval-gated merges to protected main branches.
ComputerConnectionCollect sprint phase data and generate a Sprint Retro document.
bhianerdAnalyze git commit history to generate weekly engineering retrospectives.
ignidusAnalyze Git repository history to produce a data-driven retro report.