qa-dev-loop

Name: qa-dev-loop
Availability: InStock
Author: Olivier

Run iterative QA, triage, and development loops with verified shipping.

Updated Feb 7, 2026

Search Tags:#qa #issue tracking #continuous improvement #triage #release verification #bug bash #test and fix

Ready to run

npx skills add https://github.com/thisolivier/chronolog --skill qa-dev-loop

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-dev-loop
Source: https://github.com/thisolivier/chronolog/tree/main/.claude/skills/qa-dev-loop
Command: npx skills add https://github.com/thisolivier/chronolog --skill qa-dev-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams continuously improve application quality by turning real user testing into tracked pain points, prioritized fixes, and verified releases.

Core Features & Use Cases

Iterative QA → triage → development: Exercise in-scope features, document issues with severity, then prioritize and implement only what matters next.
Structured issue tracking: Maintain a living pain-points markdown document with [todo] and [fix] items and round-based archiving.
Verification-focused shipping: Re-test fixes, run the full test suite, smoke-test the main workflow, and update documentation when behavior changes.

Quick Start

Start the QA loop for your target features by confirming the scope, pain-points location, and whether to pause for go-ahead each round.

Frequently Asked Questions about qa-dev-loop

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

FAQPage Schema

How do I set up a continuous QA loop for hardening application features?▼

You set up a continuous QA loop by confirming a pre-flight scope, tracking pain points in a living markdown document, and running phased QA, triage, development, and shipping cycles. This structured approach turns real user testing into tracked issues and verified releases.

What's the best way to prioritize bug fixes during a test and fix cycle?▼

Prioritize bug fixes by applying triage thresholds to documented issue severity from your pain-points tracking. This ensures you implement only what matters next, coordinating batched development work for verified shipping.

How does release verification work after implementing batched fixes?▼

Release verification works by re-testing implemented fixes, running the full test suite, and smoke-testing the main workflow. You then update documentation if behavior changed and archive the completed round's pain-points items.

Can I reproduce edge-case failures using an iterative issue tracking process?▼

Yes, you can reproduce edge-case failures by exercising in-scope features during the QA phase and documenting them as pain points. The iterative loop captures these failures, triages them by severity, and coordinates batched development work to resolve them.

Do I need a separate issue tracking tool to coordinate batched development work?▼

No, a separate issue tracking tool is not required. The loop maintains a living pain-points markdown document containing todo and fix items, handling round-based archiving and tracking issues directly within your development workflow.

When should I not use a structured triage and dev improvement loop?▼

Avoid a structured triage and dev improvement loop when hardening working functionality is unnecessary or when a user-confirmed pre-flight scope is absent. The process depends on iterative testing, phased execution, and round-based re-verification to deliver quality improvements.