skills.rest
ascerra-fullsend-rehearsal
ascerra-fullsend-rehearsalOFFICIAL
Explore all skills by this author →
GitHub

retro-analysis

Trace agent workflow runs and write structured improvement proposals.

Updated May 31, 2026
Search Tags:#GitHub#workflow analysis#agent workflows#retro-analysis#improvement proposals
One-click install
npx skills add https://github.com/ascerra-fullsend-rehearsal/fullsend --skill retro-analysis-ascerra-fullsend-rehearsal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro-analysis
Source: https://github.com/ascerra-fullsend-rehearsal/fullsend/tree/main/internal/scaffold/fullsend-repo/skills/retro-analysis
Command: npx skills add https://github.com/ascerra-fullsend-rehearsal/fullsend --skill retro-analysis-ascerra-fullsend-rehearsal

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of conducting retrospectives on agent workflows, helping users trace workflow runs, explore context with subagents, and write structured improvement proposals.

Core Features & Use Cases

  • Workflow Tracing: Trace the entire workflow history from a PR or issue.
  • Context Exploration: Use subagents to analyze logs, comments, and configurations.
  • Improvement Proposals: Write structured proposals for enhancing agent workflows.
  • Use Case: After a workflow run, use this Skill to identify bottlenecks and suggest improvements, enhancing the efficiency and reliability of your agent workflows.

Quick Start

Analyze the workflow of the latest PR with the command: retro-analysis analyze-pr <PR_NUMBER>

Frequently Asked Questions about retro-analysis

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

FAQPage Schema
How do I conduct a retrospective analysis on GitHub agent workflows?▼

Retrospective analysis for agent workflows involves tracing workflow runs from a PR or issue, exploring context like logs and comments with subagents, and writing structured improvement proposals to optimize automated processes.

Can I trace an agent workflow run directly from a GitHub pull request?▼

Yes, you can trace the entire workflow history from a GitHub pull request. By analyzing the PR number, the tool reviews comments, logs, and configurations to identify bottlenecks and suggest workflow improvements.

Do I need a GitHub API token to analyze agent workflows?▼

Yes, conducting retrospective analysis on agent workflows requires access to the GitHub API via the gh command-line tool, along with access to the .fullsend dispatch repository to retrieve workflow run data.

What is the best way to identify bottlenecks in automated software development workflows?▼

The best way to identify bottlenecks in automated software development workflows is to use subagents to explore run context, trace workflow history from pull requests, and generate structured proposals for enhancing workflow efficiency and reliability.

When should I use workflow tracing for agent workflows?▼

You should use workflow tracing for agent workflows after a workflow run completes, especially when you need to debug automated processes, analyze context from logs and comments, or propose structured improvements for software development pipelines.

Related Skills

Explore More Software Engineering Skills→
faccomichelefaccomichele

github-read-access

Inspect GitHub repository data, issues, pull requests, releases, and CI runs via gh CLI.

Community
Intermediate
DalimovichDalimovich

github-release-management

Automate multi-stage software releases with planning, testing, and deployment.

Community
Advanced
robertolopezlopezrobertolopezlopez
1

github-pr-comment-analysis

Group unresolved GitHub pull request comments into actionable issue sections.

Community
Advanced
dp-archivedp-archive
1.1k

trace-qa

Analyze agent execution traces to inspect steps, tool usage, and LLM calls.

Community
Intermediate