self-improvement-ci

Automated learning capture in CI pipelines that deduplicates failure patterns and proposes prevention rules.

pskoett/pskoett-ai-skillsUpdated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

104

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/pskoett/pskoett-ai-skills --skill self-improvement-ci

0

installs

0

this week

104

stars

What it does

  • Inspects PR check results and CI failures to identify recurring patterns tracked by stable pattern_key , promoting only when recurrence thresholds are met (3+ occurrences across 2+ distinct runs within 30 days)

  • Ingests learning candidates from simplify-and-harden-ci and emits machine-readable YAML output without interactive prompts, suitable for headless GitHub Actions workflows

Category

Productivity

Last updated

Apr 8, 2026

Installation Guide

How to use self-improvement-ci on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add self-improvement-ci
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/pskoett/pskoett-ai-skills --skill self-improvement-ci

Fetches self-improvement-ci from pskoett/pskoett-ai-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/self-improvement-ci

Restart Cursor to activate self-improvement-ci. Access via /self-improvement-ci in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

Self-Improvement CI

Install

npx skills add pskoett/pskoett-ai-skills/skills/self-improvement-ci

Purpose

Run self-improvement in CI without interactive chat loops:

  • Inspect PR check results and CI failures
  • Ingest learning candidates from simplify-and-harden-ci
  • Deduplicate recurring patterns by stable pattern_key
  • Emit promotion-ready suggestions for agent context/system prompts

Use self-improvement for interactive/local sessions.

Context Limitation (Important)

CI agents do not have peak task context from the original implementation session. Use this skill to aggregate recurring patterns across runs, not to infer nuanced one-off intent.

Implications:

  • Favor stable pattern_key recurrence signals over single-run conclusions
  • Require recurrence thresholds before promotion
  • Route uncertain or high-impact recommendations to interactive review

Prerequisites

  1. GitHub Actions enabled for the repository
  2. GitHub CLI authenticated (gh auth status)
  3. gh-aw installed for authoring/validation:
gh extension install github/gh-aw

CI Contract

The CI skill must:

  1. Read only PR-scoped data (checks, workflow outcomes, existing learning entries)
  2. Avoid direct code modifications in CI
  3. Emit machine-readable learning output
  4. Recommend promotion only when recurrence thresholds are met

Output Schema

self_improvement_ci:
  source:
    pr_number: 123
    commit_sha: "abc123"
  candidates:
    - pattern_key: "harden.input_validation"
      source: "simplify-and-harden-ci"
      recurrence_count: 3
      first_seen: "2026-02-01"
      last_seen: "2026-02-20"
      severity: "high"
      suggested_rule: "Validate and bound-check external inputs before use."
      promotion_ready: true
  summary:
    candidates_total: 4
    promotion_ready_total: 1
    followup_required: true

Recurrence and Promotion Rules

  • Track recurrence by pattern_key
  • Default threshold for promotion:
    • recurrence_count >= 3
    • seen in >= 2 distinct tasks/runs
    • within a 30-day window
  • Promotion targets:
    • CLAUDE.md
    • AGENTS.md
    • .github/copilot-instructions.md
    • SOUL.md / TOOLS.md when using openclaw workspace memory

Authoring Workflow (gh-aw)

Example-only templates live in references/workflow-example.md. Keep examples outside .github/workflows until you explicitly decide to enable CI automation.

When ready:

  1. Copy the template into .github/workflows/self-improvement-ci.md
  2. Customize tool access, outputs, and policy thresholds
  3. Validate:
gh aw compile --validate --strict
  1. Trigger test run manually:
gh aw run self-improvement-ci --push

Integration with Other Skills

  • Pair with simplify-and-harden-ci to ingest simplify_and_harden.learning_loop.candidates
  • Feed promoted patterns back into self-improvement memory workflow for durable prevention rules

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Steps

  1. 1Install product management skill
  2. 2Start with user story generation for known feature
  3. 3Progress to competitive analysis: research 2-3 competitors
  4. 4Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5Draft stakeholder communications and refine based on feedback
  6. 6Build template library for recurring PM tasks
  7. 7Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use when

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid when

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Related Skills

Reviews

4.451 reviews
  • A
    Aarav TandonDec 28, 2024

    Useful defaults in self-improvement-ci — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • L
    Li AgarwalDec 20, 2024

    Registry listing for self-improvement-ci matched our evaluation — installs cleanly and behaves as described in the markdown.

  • L
    Liam ParkDec 16, 2024

    self-improvement-ci reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • H
    Hassan IyerDec 16, 2024

    self-improvement-ci has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • L
    Lucas HuangNov 19, 2024

    Registry listing for self-improvement-ci matched our evaluation — installs cleanly and behaves as described in the markdown.

  • I
    Ishan GarciaNov 11, 2024

    Useful defaults in self-improvement-ci — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • S
    Sakura PerezNov 7, 2024

    I recommend self-improvement-ci for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • K
    Kabir WhiteOct 26, 2024

    Useful defaults in self-improvement-ci — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • I
    Isabella ZhangOct 10, 2024

    self-improvement-ci reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • I
    Ishan HaddadOct 2, 2024

    I recommend self-improvement-ci for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 51

1 / 6

Discussion

Comments — not star reviews
  • No comments yet — start the thread.