Workflow Skill Extraction Report: 3 shared-component adoption opportunities #49044
Closed
Replies: 3 comments
|
This discussion was automatically closed because it expired on 2026-08-06T04:47:00.868Z.
|
0 replies
|
This discussion was automatically closed because it expired on 2026-08-06T04:47:00.868Z.
|
0 replies
|
This discussion was automatically closed because it expired on 2026-08-06T04:47:00.868Z.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Workflow Skill Extraction Report
Methodology
Analyzed
/tmp/gh-aw/agent/workflow-index.json(266 workflows total, 77 existing shared components in.github/workflows/shared/) to map import frequency, engines, and tool usage. Cross-referenced high-frequency patterns against existing shared components to distinguish "needs a new component" from "component exists but is under-adopted." Deep-dived candidate workflows withgrep/globto confirm concrete duplication evidence (line numbers, package-install patterns, pricing config) before finalizing recommendations.Coverage summary
shared/shared/otlp.md(228),shared/reporting.md(53),shared/github-guard-policy.md(19),shared/gh.md(12)engine: null(likely default/copilot), 98 explicitlycopilot, 21pi, 21claude, 7codex, 1 eachantigravity/gemini/opencodeOpportunities identified (priority order)
shared/python-dataviz.mdfor matplotlib/pandas/seaborn setupshared/default-ai-credits-pricing.mdto prevent pricing failuresshared/mcp-pagination.mdDetails
1. Python data-viz setup (High priority)
12 workflows (
agentic-token-audit.md,agentic-token-trend-audit.md,api-consumption-report.md,daily-code-metrics.md,daily-experiment-report.md,daily-firewall-report.md,daily-issues-report.md,daily-news.md,daily-performance-summary.md,daily-repo-chronicle.md,prompt-clustering-analysis.md,weekly-issue-summary.md) use matplotlib/pandas/seaborn without importing the existingshared/python-dataviz.mdorshared/charts-with-trending.md. Setup approaches diverge inconsistently (pip install --target,python3 -m venv,pypy3 -m pip install), risking version drift and re-introducing solved problems (e.g.--break-system-packages). Estimated 150-300 duplicated lines removable, plus consistency of a single venv/package strategy.2. Default AI-credits pricing fallback (Medium priority)
Only 5 of 266 workflows import
shared/default-ai-credits-pricing.md. This is a latent-risk gap rather than visible duplication: workflows using less-common engines (pi: 21,codex: 7,antigravity/gemini/opencode: 1 each) are most exposed tomissing_model_pricing/unknown_model_ai_creditsfailures when a model lacks catalog pricing. Adding the 1-line import is cheap insurance against a class of intermittent, hard-to-debug failures.3. MCP pagination guidance consolidation (Low priority)
21 workflows reference
per_page/pagination manually without importingshared/mcp-pagination.md, leading to inconsistentperPagethresholds and repeated prose about the 25,000-token MCP response limit. Lower priority since duplication is prose (not executable code) and the highest-risk bulk-list cases are already covered byshared/github-mcp-pagination-wrappers.md.Impact summary
No new shared components are proposed — all three recommendations are adoption/migration tasks for components that already exist in
.github/workflows/shared/, which keeps implementation risk low (no new abstractions to validate) while still meaningfully reducing duplication and failure surface.References:
All reactions