[refactoring] Improve adoption of shared/repo-memory-standard.md — 19 workflows with inline repo-memory config

[github-actions]

Overview

shared/repo-memory-standard.md exists and provides a consistent, validated repo-memory configuration, but 19 out of 30 workflows that use repo-memory: define it inline, each slightly differently. This causes configuration drift and makes it harder to apply cross-cutting changes (e.g. default file-glob patterns, max-file-size limits).

Current State

Status	Count
Workflows using shared/repo-memory-standard.md	11
Workflows defining repo-memory: inline (without shared import)	19

Already adopting (11): copilot-agent-analysis.md, copilot-session-insights.md, audit-workflows.md, and 8 others.

High-value migration targets (standard config pattern, not using wiki/campaigns):
deep-report.md, daily-code-metrics.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.md (and more)

Workflows that likely need to stay inline (use non-standard configs like wiki: true, branch-prefix:, array ids, or custom file-glob for campaigns): daily-community-attribution.md, code-scanning-fixer.md, security-compliance.md, weekly-blog-post-writer.md, daily-code-metrics.md (uses branch-prefix:)

Typical Inline Pattern (before migration)

tools:
  repo-memory:
    branch-name: memory/my-workflow
    description: "Historical my-workflow results"
    file-glob: ["*.json", "*.jsonl", "*.csv", "*.md"]
    max-file-size: 102400
    max-patch-size: 10240

After Migration

imports:
  - uses: shared/repo-memory-standard.md
    with:
      branch-name: memory/my-workflow
      description: "Historical my-workflow results"

The shared component enforces the canonical file-glob (*.json, *.jsonl, *.csv, *.md) and default max-file-size/max-patch-size values, reducing per-workflow config noise.

Estimated Impact

• Workflows affected: ~13 (straightforward migrations; ~6 need non-standard config)
• Approximate line savings: 4–6 lines per workflow = ~52–78 lines
• Maintenance benefit: Centralised defaults for repo-memory sizing limits; any future changes apply uniformly

Migration Plan

1. Audit each of the 19 inline workflows and classify as: (a) standard config → migrate, (b) non-standard → keep inline.
2. For each standard-config workflow, replace the tools.repo-memory: block with shared/repo-memory-standard.md import (see example above).
3. For non-standard workflows (wiki, campaigns, custom globs), document the reason inline as a comment.
4. Run make recompile after migrations.
5. Optionally extend repo-memory-standard.md with additional optional inputs if common non-standard patterns emerge.

References: §25192799682

Generated by Workflow Skill Extractor · ● 2.9M · ◷

• expires on May 2, 2026, 10:47 PM UTC

[github-actions]

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · ● 20.7K · ◷