self-improvement-ci

Capture recurring failure patterns from GitHub Actions pull request checks.

2|1|Updated May 30, 2025
One-click install
npx skills add https://github.com/lvzhengbin/AI-Prompts --skill self-improvement-ci-lvzhengbin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-improvement-ci
Source: https://github.com/lvzhengbin/AI-Prompts/tree/main/skills/self-improvement-ci
Command: npx skills add https://github.com/lvzhengbin/AI-Prompts --skill self-improvement-ci-lvzhengbin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the capture of recurring failure patterns and quality signals from CI pipelines, allowing for continuous improvement without manual intervention.

Core Features & Use Cases

  • CI-only Self-Improvement: Runs without interactive chat loops, ideal for headless environments.
  • Pattern Aggregation: Identifies and deduplicates recurring issues based on stable pattern_key.
  • Learning Candidate Emission: Emits structured learning candidates for agent context and prompt improvement.
  • Use Case: Automatically analyze failed GitHub Actions runs, identify a common cause like input validation errors, and propose a durable prevention rule to be added to system prompts.

Quick Start

Use the self-improvement-ci skill to analyze pull request check results and capture recurring failure patterns.

Frequently Asked Questions about self-improvement-ci

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

FAQPage Schema
How do I automatically capture recurring failure patterns from GitHub Actions CI?

Automated CI self-improvement captures recurring failure patterns by analyzing pull request check results in CI environments. It deduplicates recurring issues using a stable pattern_key and emits structured learning suggestions for agent context and system prompts.

What's the best way to aggregate quality signals from CI pipelines without manual intervention?

Aggregating quality signals from CI pipelines without manual intervention requires a CI-only self-improvement approach. This method runs in headless environments, identifies recurring issues, and proposes durable prevention rules to be added to system prompts.

Do I need GitHub CLI authentication to analyze failed pull request checks?

Yes, analyzing failed pull request checks and capturing recurring failure patterns requires GitHub CLI authentication. You also need the gh-aw extension for authoring and validation of the structured learning candidates.

How does pattern aggregation and deduplication work for recurring CI failures?

Pattern aggregation for recurring CI failures works by identifying recurring issues and deduplicating them using a stable pattern_key. This process emits structured learning candidates that can be used to improve agent context and system prompts continuously.

Can I run continuous learning capture in headless CI environments?

Yes, you can run continuous learning capture in headless CI environments. The CI-only self-improvement mechanism operates without interactive chat loops, making it ideal for capturing recurring failure patterns automatically during pull request checks.

What are the limitations of automated learning capture in CI?

Automated learning capture in CI is limited by its dependency on GitHub CLI authentication and the gh-aw extension for authoring and validation. It is designed for headless environments and does not support interactive chat loops for real-time learning.