retro

Name: retro
Availability: InStock
Author: canpok1

Analyze session reflections and `.claude/` configuration files to create GitHub Issues.

Updated Jan 29, 2026

Search Tags:#retrospective #github issues #workflow improvement #coding session #session review #configuration analysis

Ready to run

npx skills add https://github.com/canpok1/claude-code-plugins --skill retro-canpok1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/canpok1/claude-code-plugins/tree/main/plugins/base-tools/skills/retro
Command: npx skills add https://github.com/canpok1/claude-code-plugins --skill retro-canpok1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you reflect on your work sessions, analyze configuration improvements within your .claude/ directory, and create GitHub Issues for actionable changes.

Core Features & Use Cases

Session Retrospective: Review tasks, tools, challenges, and successes from your conversation session.
Configuration Analysis: Examine .claude/ settings (CLAUDE.md, agents/, skills/) for potential improvements.
GitHub Issue Creation: Automatically generate GitHub Issues for identified improvements, including duplicate checks.
Use Case: After a complex coding session, use this Skill to document what went well, what didn't, and automatically create a GitHub Issue to refine your agent configurations for future sessions.

Quick Start

Use the retro skill to analyze the session and create a GitHub issue for any identified improvements.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I automate session retrospective and create GitHub Issues for workflow improvements?▼

To automate session retrospective and create GitHub Issues, this Skill analyzes your work session reflections and `.claude/` configuration files to identify actionable improvements, then automatically generates issues using the `gh` CLI. It performs duplicate checks before creating issues to track workflow refinements.

Can I analyze `.claude/` configuration files to refine agent and skill settings?▼

Yes, you can analyze `.claude/` configuration files to refine agent and skill settings. This Skill examines your CLAUDE.md, agents, and skills configurations to identify potential areas for improvement and documents best practices for future coding sessions.

Do I need the `gh` CLI installed to create GitHub Issues from coding session reviews?▼

Yes, you need the `gh` CLI installed to create GitHub Issues from coding session reviews. The Skill requires the GitHub CLI for GitHub integration to automatically generate and perform duplicate checks on issues for identified configuration improvements.

What's the best way to document agent performance challenges after a complex coding session?▼

The best way to document agent performance challenges is to review tasks, tools, and successes from your conversation session. This Skill examines your session reflections and `.claude/` settings to identify what went well and what didn't, then automatically creates GitHub Issues for actionable changes.

Does this session review tool check for duplicate GitHub Issues before creating new ones?▼

Yes, this session review tool checks for duplicate GitHub Issues before creating new ones. When analyzing configuration improvements within your `.claude/` directory, it performs duplicate checks during the GitHub Issue creation process to ensure actionable changes are tracked without redundancy.

When should I not use a retrospective workflow for configuration analysis?▼

You should not use a retrospective workflow for configuration analysis if you lack standard file system access to your `.claude/` directory or do not have the `gh` CLI configured for GitHub integration, as both are required for analyzing settings and creating actionable issues.