skills.rest
edfenton
edfentonCOMMUNITY
Explore all skills by this author →
Website𝕏@edfentonGitHub

retro-resolve

Batch-process open retro.md issues across all skills with audit trails.

3|1|Updated Feb 12, 2026
Search Tags:#automation#markdown#scripting#issue-tracking#retro
One-click install
npx skills add https://github.com/edfenton/claude-skills --skill retro-resolve
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro-resolve
Source: https://github.com/edfenton/claude-skills/tree/main/shared/retro-resolve
Command: npx skills add https://github.com/edfenton/claude-skills --skill retro-resolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch-process retro.md entries across all skills to close open issues efficiently.

Core Features & Use Cases

  • Discovery: Locate all retro.md files with status: open entries and summarize active concerns.
  • Resolution: Investigate root causes by reading the skill's SKILL.md and referenced files, apply fixes, and update retro entries.
  • Audit Trail: Record files changed and append a resolution note for traceability.

Quick Start

Read all retro.md files and run the resolver to fix open items across skills.

Frequently Asked Questions about retro-resolve

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

FAQPage Schema
How do I automate retro issue resolution across multiple skills?▼

To automate retro issue resolution, you can batch-process open status entries in retro.md files by investigating root causes, applying fixes, and updating the corresponding SKILL.md templates with an appended audit trail.

What is the best way to track open issues in markdown retro files?▼

Tracking open issues in markdown retro files involves scanning all retro.md entries for status: open attributes, reading the associated SKILL.md to investigate the root cause, and appending a resolution note to close the item.

Can I batch process open status entries in retro.md without manual intervention?▼

Yes, you can batch process open status entries in retro.md files automatically by discovering active concerns across the repository, applying targeted fixes to the relevant skill files, and logging the changes for traceability.

How does automated issue-tracking append an audit trail to markdown files?▼

Automated issue-tracking appends an audit trail by reading the open retro entry and corresponding SKILL.md, applying the necessary file edits to resolve the issue, and appending a resolution note recording the changes made.

Do I need any dependencies to run markdown scripting for retro issue resolution?▼

No dependencies are required to run markdown scripting for retro issue resolution, as the process relies on discovering and reading native retro.md and SKILL.md files to apply fixes directly within the repository.

Why are open retro issues still showing up after running the resolver script?▼

Open retro issues may persist if the resolver cannot read the corresponding SKILL.md to investigate the root cause, preventing it from applying fixes and appending the required resolution note to the retro.md entry.

Related Skills

Explore More Product & Management Skills→
tcfialhotcfialho

fix-my-code

Analyze incident files to construct causal chains and identify root causes.

Community
Advanced
braselogbraselog
3

review-script

Analyze Python scripts for documentation quality, coding standards, and reproducibility.

Community
Basic
anthony-chaudharyanthony-chaudhary
30

steerability-score

Quantify repository steerability with growth-invariant KPIs and guide refactoring.

Community
Advanced
Himanshu040604Himanshu040604

pinecone:cli

Manage Pinecone indexes and vector operations via terminal commands.

Community
Intermediate