Classify pull request findings by detectability and generate checklist improvement proposals.
npx skills add https://github.com/mori-shin-x/artgraph --skill issue-retro
Please help me install this Agent Skill. Skill: issue-retro Source: https://github.com/mori-shin-x/artgraph/tree/main/.claude/skills/issue-retro Command: npx skills add https://github.com/mori-shin-x/artgraph --skill issue-retro
This Skill addresses the common issue of recurring bugs and process gaps by systematically analyzing completed PR findings to improve future development workflows.
Run the issue-retro skill by providing the URL of the completed pull request to generate a retrospective analysis and checklist update proposal.
High-intent search queries and answers about installing and using this skill.
To turn pull request review comments into process improvements, analyze completed PR findings to classify them by detectability and update your project checklists. This categorizes findings into those detectable via existing criteria, those needing new rules, and inherently unpredictable issues.
Preventing recurring bugs found in code reviews requires a structured feedback loop that audits review comments against existing pre-implementation checklists. By classifying findings by detectability, you can add missing criteria to prevent similar defects in future development cycles.
Classifying code review findings to update your QA checklist involves comparing PR review comments against existing project documentation. This comparative analysis identifies gaps, categorizing findings into detectable issues, those requiring new checklist criteria, and unpredictable edge cases.
Yes, you can use PR metadata to refine a software engineering pre-implementation checklist. By analyzing pull request metadata and existing checklist documentation, the system performs comparative analysis to generate targeted process improvement proposals.
You need a retrospective analysis for your software development workflow after complex feature releases or when recurring process gaps appear. It systematically audits completed PR findings and E2E test failures to determine if your Step 0-pre checklist needs updates.
A limitation of analyzing PR findings for quality assurance is that some defects are inherently unpredictable and cannot be prevented by updating checklists. Additionally, this analysis requires access to existing project checklist documentation to generate accurate improvement proposals.
lossyrobPost finalized review comments from ReviewComments.md to GitHub as pending reviews.
bamechoCoordinate engineering workflows through Plan, Work, Review, and Compound steps.
DbillionaerOrchestrate multi-phase testing and quality assurance for software development.
santosomarDetect null dereferences, type mismatches, and control flow bugs via static analysis.
