Overview
Multiple daily/scheduled workflows detect code quality issues and create GitHub issues (not discussions) but duplicate the same boilerplate frontmatter. A shared/daily-issue-base.md component — analogous to the existing shared/daily-audit-base.md — would consolidate this pattern.
Current Usage (6 confirmed + ~6 partial)
Workflows with the complete pattern (tracker-id + skip-if-match: is:issue + create-issue + reporting.md + activation-app.md):
| Workflow |
Lines saved (est.) |
architecture-guardian.md |
~15 |
breaking-change-checker.md |
~12 |
daily-file-diet.md |
~12 |
daily-testify-uber-super-expert.md |
~12 |
refactoring-cadence.md |
~15 |
spec-librarian.md |
~12 |
Partial adopters (tracker-id + create-issue, missing skip-if-match or activation-app): daily-cache-strategy-analyzer, deep-report, workflow-normalizer, daily-skill-optimizer, copilot-token-optimizer, discussion-task-miner.
Proposed Shared Component: shared/daily-issue-base.md
---
# Bundle for daily/scheduled code quality workflows that create GitHub issues.
# Bundles: activation-app + reporting + standardized create-issue safe-outputs.
#
# Usage:
# imports:
# - uses: shared/daily-issue-base.md
# with:
# title-prefix: "[my-workflow] "
# expires: "2d"
# labels: [automation, cookie]
import-schema:
title-prefix:
type: string
required: true
description: "Title prefix for created issues, e.g. '[my-workflow] '"
expires:
type: string
default: "2d"
description: "How long to keep issues before expiry"
labels:
type: array
default: [automated-analysis, cookie]
description: "Labels to apply to created issues"
imports:
- shared/activation-app.md
- shared/reporting.md
safe-outputs:
create-issue:
expires: ${{ github.aw.import-inputs.expires }}
title-prefix: ${{ github.aw.import-inputs.title-prefix }}
labels: ${{ github.aw.import-inputs.labels }}
max: 1
noop:
---
Example Usage (After Migration)
imports:
- uses: shared/daily-issue-base.md
with:
title-prefix: "[architecture-guardian] "
expires: "2d"
labels: [architecture, automated-analysis, cookie]
Estimated Impact
- ~12 workflows immediately benefit (6 direct + 6 partial adopters)
- ~15 lines removed per workflow on average
- Maintenance benefit: Changes to create-issue defaults, noop, or activation-app propagate automatically
Migration Plan
- Create
shared/daily-issue-base.md with the schema above
- Recompile all existing workflows to verify they compile cleanly:
make recompile
- For each of the 6 confirmed workflows: replace
imports: shared/activation-app.md + shared/reporting.md + inline safe-outputs.create-issue block with the new shared import
- Test compilation of each migrated workflow
- Submit single PR with all migrations
References: §25163549011
Generated by Workflow Skill Extractor · ● 4.3M · ◷
Overview
Multiple daily/scheduled workflows detect code quality issues and create GitHub issues (not discussions) but duplicate the same boilerplate frontmatter. A
shared/daily-issue-base.mdcomponent — analogous to the existingshared/daily-audit-base.md— would consolidate this pattern.Current Usage (6 confirmed + ~6 partial)
Workflows with the complete pattern (
tracker-id+skip-if-match: is:issue+create-issue+reporting.md+activation-app.md):architecture-guardian.mdbreaking-change-checker.mddaily-file-diet.mddaily-testify-uber-super-expert.mdrefactoring-cadence.mdspec-librarian.mdPartial adopters (tracker-id + create-issue, missing skip-if-match or activation-app):
daily-cache-strategy-analyzer,deep-report,workflow-normalizer,daily-skill-optimizer,copilot-token-optimizer,discussion-task-miner.Proposed Shared Component:
shared/daily-issue-base.mdExample Usage (After Migration)
Estimated Impact
Migration Plan
shared/daily-issue-base.mdwith the schema abovemake recompileimports: shared/activation-app.md + shared/reporting.md+ inlinesafe-outputs.create-issueblock with the new shared importReferences: §25163549011