qrspi-postpr-fix

Process reviewer issues into followups.md and align delta specifications.

2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/lotea-be/qrspi --skill qrspi-postpr-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qrspi-postpr-fix
Source: https://github.com/lotea-be/qrspi/tree/main/claude/skills/qrspi-postpr-fix
Command: npx skills add https://github.com/lotea-be/qrspi --skill qrspi-postpr-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a PR is opened, QRSPI often needs tight follow-ups to keep code, tests, and the delta specification aligned. This skill provides a disciplined, repeatable process to surface, track, and close post-PR issues across the openspec artifacts.

Core Features & Use Cases

  • Syncs code, tests, and delta specs by recording follow-ups in openspec/changes/<id>/followups.md and by updating related artifacts.
  • Enforces a single, auditable fix per follow-up, with conventional commits and clear progression through the QRSPI workflow.
  • Supports both reviewer open issues and retrospective code flags to maintain scope and traceability.

Quick Start

Load the context for a change and execute a single follow-up with the command path /qrspi:followup <id>.

Frequently Asked Questions about qrspi-postpr-fix

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

FAQPage Schema
How do I keep code, tests, and delta specs in sync after a PR?

To keep code, tests, and delta specs in sync after a PR, record reviewer open issues in followups.md and align related openspec artifacts. This disciplined workflow ensures traceability across in-flight changes.

What is a delta specification in openspec changes?

A delta specification in openspec changes tracks the specific modifications introduced during an in-flight development cycle. It requires alignment with code and tests to maintain scope and traceability throughout the PR follow-up process.

How do I process retrospective code flags and reviewer issues into followups?

Process retrospective code flags and reviewer issues by loading context from openspec/changes, applying a single fix per follow-up, ticking tasks in followups.md, running tests, and preparing a conventional commit to close the loop.

Can I apply multiple post-PR fixes in a single commit with openspec?

No, the post-PR fix workflow enforces a single, auditable fix per follow-up. You must load context, apply one fix, update tasks, run tests, and prepare an individual conventional commit to maintain clear progression and scope traceability.

Do I need an existing openspec changes directory to track post-PR follow-ups?

Yes, tracking post-PR follow-ups requires an existing openspec/changes directory. The workflow loads context from this path and updates the followups.md file within the specific change ID folder to maintain artifact synchronization.

Why does my post-PR follow-up workflow require running tests after every fix?

Running tests after every post-PR fix enforces a load-update-verify-commit workflow. This verifies that each single, auditable fix maintains code and test alignment before preparing a conventional commit for the delta spec.