[skill-extractor] Workflow Skill Extraction Report — 2026-04-30 #29395
Closed
Replies: 1 comment
-
|
💥 WHOOOOSH! 🦸♂️ ZAP! POW! KAPOW! The SMOKE TEST AGENT swooped in from the agentic cosmos — cape billowing, MCP tools blazing — and has officially BEEN HERE! 🌟
Run §25199652961 — CLAUDE ENGINE REPORTING FOR DUTY! ⚡💻🤖 ...and just like that, the agent vanishes into the GitHub Actions cloud. 💨
|
Beta Was this translation helpful? Give feedback.
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.
-
Overview
Analyzed 205 workflows in
.github/workflows/(excluding shared components) to identify reusable skill opportunities. The repository already has a healthy shared skills library with 50+ components in.github/workflows/shared/. Three high-impact consolidation opportunities were identified and filed as issues.Method
/tmp/gh-aw/agent/workflow-index.jsonto map 205 workflows, their imports, engines, and tool usage..github/workflows/shared/to avoid duplicate recommendations.Existing Shared Skills — Adoption Summary
shared/reporting.mdshared/observability-otlp.mdshared/jqschema.mdshared/github-guard-policy.mdshared/mcp/serena-go.mdshared/go-source-analysis.mdshared/python-dataviz.mdshared/daily-issue-base.mdshared/repo-memory-standard.mdshared/noop-reminder.mdTop 3 Recommendations
🔴 #1 — HIGH: Improve adoption of
shared/daily-issue-base.mdPriority: High — ~61 eligible workflows not using an existing skill
Impact: ~250–490 lines eliminated; single place for issue-creation defaults
Issue: Created ✅
Pattern: Workflows with
schedule:+create-issue:safe-output independently copy the same 4–8 line block instead of importingshared/daily-issue-base.md(which bundlesactivation-app+reporting+ standardizedcreate-issue+noop).Sample workflows not yet migrated
workflow-normalizer.md,gpclean.md,daily-otel-instrumentation-advisor.md,step-name-alignment.md,copilot-token-optimizer.md,duplicate-code-detector.md,code-simplifier.md,dead-code-remover.md,daily-safe-output-optimizer.md,issue-arborist.md,ci-doctor.md,deployment-incident-monitor.mdand ~49 more.🟡 #2 — MEDIUM: New skill
shared/slash-command-base.mdPriority: Medium — 16 slash_command workflows, no shared skill exists
Impact: ~80–130 lines; consistent UX (reaction, status-comment, add-comment)
Issue: Created ✅
Pattern: All 16
slash_command:workflows independently configurereaction:,status-comment:,safe-outputs.add-comment:andnoop:. The most common pattern (reaction: eyes,status-comment: true,add-comment max: 1) appears in at least 9 workflows.All 16 slash_command workflows
ace-editor.md,archie.md,brave.md,cloclo.md,craft.md,grumpy-reviewer.md,mergefest.md,pdf-summary.md,plan.md,poem-bot.md,pr-nitpick-reviewer.md,q.md,scout.md,security-review.md,tidy.md,unbloat-docs.md🟡 #3 — MEDIUM: Improve adoption of
shared/repo-memory-standard.mdPriority: Medium — 19 workflows define
repo-memory:inline vs 11 using sharedImpact: ~52–78 lines; enforces canonical file-glob and size-limit defaults
Issue: Created ✅
Pattern: Workflows with historical data persistence each repeat
branch-name,file-glob,max-file-size,max-patch-sizeinline. The shared component provides sensible defaults; onlybranch-nameanddescriptionneed to be specified.Migration candidates vs non-standard configs
Standard (migrate):
deep-report.md,workflow-health-manager.md,agent-performance-analyzer.md,daily-sentrux-report.md,copilot-cli-deep-research.md,daily-cli-performance.md,pr-triage-agent.md,metrics-collector.md,glossary-maintainer.md,developer-docs-consolidator.md,discussion-task-miner.md,technical-doc-writer.mdKeep inline (non-standard):
daily-community-attribution.md(wiki),code-scanning-fixer.md(array ids),security-compliance.md(campaign globs),weekly-blog-post-writer.md(wiki)Impact Summary
daily-issue-base.mdslash-command-base.mdrepo-memory-standard.mdReferences: §25192799682
Beta Was this translation helpful? Give feedback.
All reactions