skills/learning-aggregator-ci/SKILL.md
[Beta] CI-only learning aggregation workflow using gh-aw (GitHub Agentic Workflows). Scans .learnings/ files on a schedule, groups entries by pattern_key, identifies promotion-ready patterns, and posts a gap report as a PR or issue comment. Use when: you want automated cross-session pattern detection in CI/headless pipelines without interactive prompts. For interactive use, use learning-aggregator.
npx skillsauth add pskoett/pskoett-ai-skills learning-aggregator-ciInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
gh skill install pskoett/pskoett-skills learning-aggregator-ci
For interactive sessions, use:
gh skill install pskoett/pskoett-skills learning-aggregator
Fallback using the Agent Skills CLI:
npx skills add pskoett/pskoett-skills/skills/learning-aggregator-ci
npx skills add pskoett/pskoett-skills/skills/learning-aggregator
Runs the outer loop's inspect step in CI. Reads accumulated .learnings/ files, groups entries by pattern_key, computes cross-session recurrence, and produces a ranked gap report — all without human interaction.
The interactive learning-aggregator skill is designed for in-session use where the user can review and act on findings immediately. This CI variant runs on a schedule (weekly, per-sprint, or on-demand) and posts its findings as a GitHub issue comment for async review.
CI agents do not have session context. They cannot see what the user is currently working on or what task area is relevant. The CI variant scans all .learnings/ entries without relevance filtering. The gap report is comprehensive rather than targeted.
gh CLI authenticated with repo accessgh-aw extension installed (gh extension install github/gh-aw, v0.40.1+).learnings/ directory with structured entries from self-improvementHard rules for headless execution:
.learnings/ files, project instruction files (CLAUDE.md, AGENTS.md, .github/copilot-instructions.md), or any repo fileslearning_aggregator_ci key.learnings/ state produces the same gap reportreferences/workflow-example.md into .github/workflows/learning-aggregator-ci.mdweekly on mondays)gh aw compile (optionally add --actionlint --zizmor for full security scan)cache-memory: stores aggregation state (pattern groups, recurrence counts) across runs. Survives up to 90 days in Actions cache. Avoids re-scanning unchanged entries on every run.call-workflow: triggers eval-creator-ci after aggregation completes to create evals from newly promoted patterns. Compile-time fan-out with proper dependency wiring.upload-artifact: persists the gap report YAML for consumption by downstream workflows or human review.The CI agent follows these rules in order:
.learnings/: LEARNINGS.md, ERRORS.md, FEATURE_REQUESTS.mdPattern-Key, Recurrence-Count, First-Seen, Last-Seen, Priority, Status, Area, Related Files, TagsPattern-Key (exact match only — no fuzzy grouping in CI)Pattern-Key as ungroupedlearning_aggregator_cilearning_aggregator_ci:
version: "0.1.0"
source:
run_id: "<workflow run ID>"
trigger: "schedule | workflow_dispatch | issue_comment"
scan_date: "YYYY-MM-DD"
scan:
entries_total: 42
entries_with_pattern_key: 35
entries_ungrouped: 7
patterns_found: 18
promotion_ready: 3
approaching_threshold: 5
promotion_ready:
- pattern_key: "harden.input_validation"
recurrence_count: 5
distinct_tasks: 3
window_days: 21
priority: "high"
gap_type: "knowledge_gap"
area: "backend"
evidence:
- "LRN-20260301-001: Missing bounds check on pagination params"
- "ERR-20260308-002: Unconstrained string length caused OOM"
- "LRN-20260315-003: API params not validated before DB query"
recommended_action: "Add to project instruction files: Always validate and bound-check external inputs before use"
eval_candidate: true
approaching:
- pattern_key: "simplify.dead_code"
recurrence_count: 2
distinct_tasks: 1
priority: "low"
needs: "1 more distinct task"
ungrouped:
- id: "LRN-20260320-005"
summary: "Discovered undocumented rate limit on external API"
recommendation: "Assign pattern_key for future tracking"
stale:
- pattern_key: "harden.error_handling"
last_seen: "2025-12-01"
recommendation: "Dismiss — not seen in 90+ days"
summary:
promotion_ready_total: 3
approaching_total: 5
ungrouped_total: 7
stale_total: 1
followup_required: true
| Output | Destination | Content |
|--------|------------|---------|
| Gap report | Issue comment or new issue | Human-readable summary with promotion candidates and evidence |
| YAML artifact | Workflow artifact | Machine-readable learning_aggregator_ci payload |
| Check annotation | Check run summary | Count of promotion-ready and approaching patterns |
Recommended: weekly schedule + manual dispatch
on:
schedule:
- cron: '0 9 * * 1' # Monday 9am UTC
workflow_dispatch:
issue_comment:
types: [created]
The schedule ensures regular outer-loop cadence. Manual dispatch allows on-demand runs after incidents or sprints. Issue comment trigger allows /aggregate-learnings commands.
self-improvement and self-improvement-ci — produce .learnings/ entriessimplify-and-harden-ci — produces learning_loop.candidates consumed by self-improvement-ciself-improvement → .learnings/*.md
↓
learning-aggregator-ci (scheduled)
↓
gap report (issue comment + artifact)
↓
harness-updater (interactive, human-gated)
↓
eval-creator-ci (creates evals from promoted patterns)
| Aspect | Interactive (learning-aggregator) | CI (learning-aggregator-ci) |
|--------|------|------|
| Trigger | Manual or session-start | Scheduled cron or workflow_dispatch |
| Relevance filter | Filters by current task area | Scans all entries (no task context) |
| Grouping | Conservative + area/tag matching | Pattern-key exact match only |
| Output | In-session gap report | Issue comment + YAML artifact |
| Human interaction | User reviews inline | Async review via GitHub |
| Scope | Current session context | Full .learnings/ history |
development
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or the loop cap is reached. Use when: implementing features from a spec or plan, hardening existing code, fixing a batch of issues, or any multi-file task that benefits from a build-verify-fix cycle.
tools
Active runtime recovery for coding agents: when something breaks mid-task, diagnose the root cause, write a fix, VERIFY by re-running the broken thing, then file a `HEAL-` entry to `.learnings/HEALS.md` with proof. Use whenever a command, test, build, or lint fails or exits non-zero; on missing tooling, dependency/lockfile mismatch, wrong runtime version, venv or permission errors, port conflicts, dirty git state, or a missing `.env`; when the agent needs a helper or one-off script that doesn't exist yet; when an external API, tool, or MCP errors or rate-limits; or when a test flakes. Search `HEALS.md` by `Pattern-Key` first — most heals are recurrences, so increment `Recurrence-Count` instead of duplicating. Verify is mandatory: mark `pending-verify` honestly if sandboxed, `abandoned` if the fix can't be made to work. Pairs with `self-improvement` (which promotes recurring heals to durable memory) but owns the verify-before-persist discipline self-improvement doesn't.
development
Control-plane workflow for coordinating multi-agent, multi-session project work from a single Codex, GitHub Copilot, or agent-app control session. Use this skill whenever the user asks to orchestrate agents, create or steer worker sessions, run a workflow-like effort, fan out audits/research/migrations, coordinate parallel implementation streams, monitor other project sessions, or compare this control-session pattern to Claude Code dynamic workflows. This skill is especially relevant when the current session can spawn persistent project sessions and those sessions can spawn their own subagents, creating a two-level orchestration hierarchy.
tools
Active runtime recovery for coding agents: when something breaks mid-task, diagnose the root cause, write a fix, VERIFY by re-running the broken thing, then file a `HEAL-` entry to `.learnings/HEALS.md` with proof. Use whenever a command, test, build, or lint fails or exits non-zero; on missing tooling, dependency/lockfile mismatch, wrong runtime version, venv or permission errors, port conflicts, dirty git state, or a missing `.env`; when the agent needs a helper or one-off script that doesn't exist yet; when an external API, tool, or MCP errors or rate-limits; or when a test flakes. Search `HEALS.md` by `Pattern-Key` first — most heals are recurrences, so increment `Recurrence-Count` instead of duplicating. Verify is mandatory: mark `pending-verify` honestly if sandboxed, `abandoned` if the fix can't be made to work. Pairs with `self-improvement` (which promotes recurring heals to durable memory) but owns the verify-before-persist discipline self-improvement doesn't.