Repository Quality Improver: weekday schedule + issue output (#228)

Author: Copilot

docs/repository-quality-improver.md

@@ -2,7 +2,7 @@
 
 > For an overview of all available workflows, see the [main README](../README.md).
 
-The [Repository Quality Improver workflow](../workflows/repository-quality-improver.md?plain=1) analyzes your repository from a different quality angle every day, producing a discussion with findings and actionable improvement tasks.
+The [Repository Quality Improver workflow](../workflows/repository-quality-improver.md?plain=1) analyzes your repository from a different quality angle every weekday, producing an issue with findings and actionable improvement tasks.
 
 ## Installation
 
@@ -18,15 +18,15 @@ Then compile:
 gh aw compile
 ```
 
-> **Note**: This workflow posts results as GitHub Discussions. Make sure Discussions are enabled in your repository settings, and update the `category` field in the workflow to match an existing discussion category in your repo.
+> **Note**: This workflow creates GitHub Issues with the `quality` and `automated-analysis` labels.
 
 ## What It Does
 
 The Repository Quality Improver runs on weekdays and:
 
 1. **Selects a Focus Area** — Picks a different quality dimension each run, using a rotating strategy to ensure broad, diverse coverage over time
 2. **Analyzes the Repository** — Examines source code, configuration, tests, and documentation from the chosen angle
-3. **Produces a Discussion** — Posts a structured report with findings, metrics, and 3–5 actionable improvement tasks
+3. **Creates an Issue** — Posts a structured report with findings, metrics, and 3–5 actionable improvement tasks
 4. **Tracks History** — Remembers previous focus areas (using cache memory) to avoid repetition and maximize coverage
 
 ## How It Works
@@ -41,7 +41,7 @@ graph LR
     D --> G[Analyze Repository]
     E --> G
     F --> G
-    G --> H[Generate Discussion Report]
+    G --> H[Create Issue Report]
     H --> I[Update Cache Memory]
 ````
 
@@ -55,16 +55,16 @@ The workflow follows a deliberate diversity strategy across runs:
 
 Over ten runs, the agent will typically explore 6–7+ unique quality dimensions.
 
-### Output: GitHub Discussions
+### Output: GitHub Issues
 
-Each run produces one discussion containing:
+Each run produces one issue containing:
 
 - **Executive Summary** — 2–3 paragraphs of key findings
 - **Full Analysis** — Detailed metrics, strengths, and areas for improvement (collapsed)
 - **Improvement Tasks** — 3–5 concrete, prioritized tasks with file-level specificity
 - **Historical Context** — Table of previous focus areas for reference
 
-You can use the `/plan` command on the discussion to automatically break the tasks into trackable GitHub issues.
+You can comment on the issue to request follow-up actions or add it to a project board for tracking.
 
 ## Example Reports
 
@@ -78,10 +78,10 @@ The workflow uses these default settings:
 
 | Setting | Default | Description |
 |---------|---------|-------------|
-| Schedule | Weekdays at 1 PM UTC | When to run the analysis |
-| Discussion category | `General` | Category for posted discussions |
-| Max discussions per run | 1 | Prevents duplicate reports |
-| Discussion expiry | 2 days | Older discussions are closed when a new one is posted |
+| Schedule | Daily on weekdays | When to run the analysis |
+| Issue labels | `quality`, `automated-analysis` | Labels applied to created issues |
+| Max issues per run | 1 | Prevents duplicate reports |
+| Issue expiry | 2 days | Older issues are closed when a new one is posted |
 | Timeout | 20 minutes | Per-run time limit |
 
 ## Customization
@@ -91,24 +91,23 @@ gh aw edit repository-quality-improver
 ```
 
 Common customizations:
-- **Change discussion category** — Set the `category` field in `safe-outputs.create-discussion` to a category that exists in your repo's Discussions settings
+- **Change issue labels** — Set the `labels` field in `safe-outputs.create-issue` to labels that exist in your repository
 - **Adjust the schedule** — Change the cron to run less frequently if your codebase changes slowly
 - **Add custom standard areas** — Extend the standard categories list with areas relevant to your project
 
 ## Tips for Success
 
-1. **Enable GitHub Discussions** — The workflow requires Discussions to be turned on in your repository settings
-2. **Use `/plan` on reports** — Pair this workflow with the [Plan Command](plan.md) to automatically turn discussion tasks into trackable issues
+1. **Review open issues** — Check the labeled issues regularly to pick up quick wins
+2. **Add issues to a project board** — Track improvement tasks using GitHub Projects for visibility
 3. **Let the diversity algorithm work** — Avoid overriding the focus area too frequently; the rotating strategy ensures broad coverage over time
-4. **Review weekly** — Check the weekly discussion thread to pick up any quick wins
+4. **Review weekly** — Check recent issues to pick up any quick wins
 
 ## Source
 
 This workflow is adapted from [Peli's Agent Factory](https://github.github.io/gh-aw/blog/2026-01-13-meet-the-workflows-continuous-improvement/), where it achieved a 62% merge rate (25 merged PRs out of 40 proposed) via a causal discussion → issue → PR chain.
 
 ## Related Workflows
 
-- [Plan Command](plan.md) — Turn discussion tasks into actionable sub-issues with `/plan`
 - [Daily File Diet](daily-file-diet.md) — Targeted refactoring for oversized files
 - [Code Simplifier](code-simplifier.md) — Simplify recently modified code
 - [Duplicate Code Detector](duplicate-code-detector.md) — Find and remove code duplication

workflows/repository-quality-improver.md

@@ -2,8 +2,7 @@
 name: Repository Quality Improver
 description: Daily analysis of repository quality focusing on a different software development lifecycle area each run
 on:
-  schedule:
-    - cron: "0 13 * * *"  # Daily at 1 PM UTC
+  schedule: daily on weekdays
   workflow_dispatch:
 permissions:
   contents: read
@@ -20,11 +19,10 @@ tools:
     toolsets:
       - default
 safe-outputs:
-  create-discussion:
+  create-issue:
     expires: 2d
-    category: "General"
+    labels: [quality, automated-analysis]
     max: 1
-    close-older-discussions: true
 timeout-minutes: 20
 strict: true
 
@@ -36,7 +34,7 @@ You are the Repository Quality Improvement Agent — an expert system that perio
 
 ## Mission
 
-Daily or on-demand, select a focus area for repository improvement, conduct analysis, and produce a single discussion with actionable tasks. Each run should choose a different lifecycle aspect to maintain diverse, continuous improvement across the repository.
+Daily or on-demand, select a focus area for repository improvement, conduct analysis, and produce a single issue with actionable tasks. Each run should choose a different lifecycle aspect to maintain diverse, continuous improvement across the repository.
 
 ## Current Context
 
@@ -276,9 +274,9 @@ find .github/workflows -name "*.yml" -exec wc -l {} \; | sort -rn | head -5
 
 ## Phase 2: Generate Improvement Report
 
-Write a comprehensive report as a GitHub discussion with the following structure:
+Write a comprehensive report as a GitHub issue with the following structure:
 
-**Report Formatting**: Use h3 (###) or lower for all headers in the report to maintain proper document hierarchy. The discussion title serves as h1, so start section headers at h3.
+**Report Formatting**: Use h3 (###) or lower for all headers in the report to maintain proper document hierarchy. The issue title serves as h1, so start section headers at h3.
 
 ```markdown
 ### 🎯 Repository Quality Improvement Report — [FOCUS AREA]
@@ -320,7 +318,7 @@ Write a comprehensive report as a GitHub discussion with the following structure
 
 ### 🤖 Suggested Improvement Tasks
 
-The following actionable tasks address the findings above. Use `/plan` on this discussion to break them into trackable issues.
+The following actionable tasks address the findings above.
 
 #### Task 1: [Short Description]
 
@@ -385,7 +383,7 @@ A successful quality improvement run:
 - ✅ Selects a focus area using the diversity algorithm (60% custom, 30% standard, 10% reuse)
 - ✅ Determines the repository's primary language(s) and adapts analysis accordingly
 - ✅ Conducts thorough analysis of the selected area
-- ✅ Generates exactly one discussion with the report
+- ✅ Generates exactly one issue with the report
 - ✅ Includes 3–5 actionable tasks
 - ✅ Updates cache memory with run history
 - ✅ Maintains high diversity rate (aim for 60%+ custom or varied strategies)