skills.rest
evanharmon1
evanharmon1COMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Audit GitHub pull requests and issues for status updates and pending tasks.

2|Updated Feb 23, 2026
Search Tags:#automation#workflow#task management#productivity#github#retrospective
One-click install
npx skills add https://github.com/evanharmon1/harmon-devkit --skill retro-evanharmon1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/evanharmon1/harmon-devkit/tree/main/ai/skills/universal/retro
Command: npx skills add https://github.com/evanharmon1/harmon-devkit --skill retro-evanharmon1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of session fragmentation by consolidating loose ends, tracking progress on GitHub issues and PRs, and identifying necessary follow-up actions before closing a development session.

Core Features & Use Cases

  • Session Reconciliation: Automatically audits all PRs and issues touched during the session to verify their current state.
  • Loose End Tracking: Identifies uncommitted git changes, unresolved review threads, and pending TODOs.
  • Status Reporting: Generates clean, actionable status tables for PRs and issues to ensure nothing is left in an ambiguous state.

Quick Start

Invoke the retro skill at the end of your coding session to generate a summary of your work and identify any remaining tasks.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I track uncommitted git changes and unresolved GitHub PRs after a coding session?▼

A session retrospective audits GitHub pull requests and issues to verify their current state. It automatically identifies uncommitted git changes, unresolved review threads, and pending development tasks into a status report.

What is the best way to generate a status summary for GitHub issues and pull requests?▼

Performing an end-of-session retrospective generates clean status tables for GitHub issues and PRs. It audits active git branches and repository metadata to ensure all development work is accounted for and properly tracked.

Do I need the GitHub CLI installed to audit pull requests and issues for status updates?▼

Yes, you need the GitHub CLI and git installed to audit pull requests and issues. The retrospective requires these tools to verify PR states, issue assignments, and local repository status across active branches.

Can I use a retrospective to identify pending development tasks across local git branches?▼

Yes, a retrospective operates across active git branches and GitHub repository metadata to identify pending development tasks. It ensures all work is accounted for and properly tracked before closing your development session.

Why does session fragmentation make tracking GitHub issue progress difficult?▼

Session fragmentation scatters progress across multiple branches, leaving work in an ambiguous state. An end-of-session retrospective solves this by consolidating loose ends and tracking progress on GitHub issues and PRs.

Related Skills

Explore More Software Engineering Skills→
basilisk-labsbasilisk-labs
72

agentplane-task-closure-recovery

Diagnose and resolve Agentplane task synchronization failures with Git and PR states.

Official
Advanced
hmzainjamilhmzainjamil
1

Monday.com Automation

Automate Monday.com board operations, workflow rules, and cross-board task coordination.

Community
Advanced
alpoxdevalpoxdev
3

git-issue

Automates GitHub issue creation and links local branches to them.

Community
Advanced
alistairhendersoninfoalistairhendersoninfo

pr-status

Aggregate open pull requests and issues from GitHub via gh CLI.

Community
Intermediate