iteration-tracker

Test iteration tracking extracts test results from GitHub issue comments, records outcomes per iteration, and maintains a history of passes and failures. This lets you identify repeat failures, track when issues were introduced, and manage re-testing workflows from dev merge through staging validation.

Yes. The Skill triggers repeat-failure alerts after multiple consecutive failures, automatically recording failure reasons and suggesting corrective actions. This reduces manual monitoring and flags patterns that need investigation.

The Skill parses issue comments via GitHub CLI to extract iteration records, then generates Markdown-formatted reports showing test outcomes and trends. Reports display iteration history at a glance so QA teams see progress and blockers without manual aggregation.

Iteration-tracker extracts test results, timestamps, and failure patterns directly from issue comments. It organizes this data into structured iteration records linked to specific GitHub issues, enabling automated tracking without external dashboards or manual log entry.

Yes. The Skill is designed for QA workflows that span CI stages—from dev merges to staging tests—and records results at each iteration. Integration with GitHub issues and CLI-based comment parsing fits standard CI automation patterns.