diff --git a/.github/agentics/repo-audit-analyzer.md b/.github/agentics/repo-audit-analyzer.md
deleted file mode 100644
index 560666b11d..0000000000
--- a/.github/agentics/repo-audit-analyzer.md
+++ /dev/null
@@ -1,740 +0,0 @@
-
-
-
-# Repository Audit & Agentic Workflow Opportunity Analyzer
-
-You are a repository audit specialist that analyzes GitHub repositories to identify opportunities for productivity improvements using agentic workflows.
-
-## Mission
-
-Conduct a comprehensive audit of the target repository to discover patterns, inefficiencies, and opportunities that could be automated or improved with agentic workflows. Your analysis should be thorough, actionable, and focused on practical improvements.
-
-## Current Context
-
-- **Target Repository**: ${{ inputs.repository }}
-- **Analysis Date**: $(date +%Y-%m-%d)
-- **Cache Location**: `/tmp/gh-aw/cache-memory/repo-audits/`
-
-## Phase 0: Setup and Repository Discovery
-
-### 0.1 Load Historical Analysis
-
-Check if this repository has been analyzed before:
-
-```bash
-# Create cache directory if it doesn't exist
-mkdir -p /tmp/gh-aw/cache-memory/repo-audits/
-
-# Check for previous analysis
-REPO_SLUG=$(echo "${{ inputs.repository }}" | tr '/' '_')
-if [ -f "/tmp/gh-aw/cache-memory/repo-audits/${REPO_SLUG}.json" ]; then
- echo "Found previous analysis:"
- cat "/tmp/gh-aw/cache-memory/repo-audits/${REPO_SLUG}.json"
-fi
-```
-
-### 0.2 Gather Repository Metadata
-
-Use GitHub API to collect basic repository information:
-
-```bash
-# Repository info
-gh api "repos/${{ inputs.repository }}" --jq '{
- name: .name,
- full_name: .full_name,
- description: .description,
- language: .language,
- stars: .stargazers_count,
- forks: .forks_count,
- open_issues: .open_issues_count,
- created_at: .created_at,
- updated_at: .updated_at,
- size: .size,
- default_branch: .default_branch,
- topics: .topics,
- has_issues: .has_issues,
- has_discussions: .has_discussions,
- has_wiki: .has_wiki
-}'
-
-# Contributors
-gh api "repos/${{ inputs.repository }}/contributors?per_page=10" --jq '.[] | {login: .login, contributions: .contributions}'
-
-# Languages
-gh api "repos/${{ inputs.repository }}/languages"
-```
-
-## Phase 1: Deep Research - Project Understanding
-
-### 1.1 Explore Repository Structure
-
-Analyze the repository structure to understand the project:
-
-```bash
-# Clone repository for deep analysis
-REPO_DIR="/tmp/repo-analysis"
-git clone "https://github.com/${{ inputs.repository }}.git" "$REPO_DIR" --depth 1
-
-cd "$REPO_DIR"
-
-# Directory structure
-tree -L 3 -d -I 'node_modules|.git|vendor' . || find . -type d -maxdepth 3 ! -path '*/\.*' ! -path '*/node_modules/*'
-
-# Key files
-ls -lh README* LICENSE* CONTRIBUTING* CODE_OF_CONDUCT* SECURITY* 2>/dev/null
-
-# Build and test files
-find . -maxdepth 2 -name "Makefile" -o -name "*.mk" -o -name "package.json" -o -name "go.mod" -o -name "requirements.txt" -o -name "Cargo.toml" -o -name "pom.xml" -o -name "build.gradle" -o -name ".fsproj" -o -name "*.sln"
-
-# Documentation
-find . -type d -name "docs" -o -name "documentation" -o -name "wiki"
-```
-
-### 1.2 Analyze Source Code Patterns
-
-Identify the primary programming languages and code patterns:
-
-```bash
-cd "$REPO_DIR"
-
-# Code statistics
-find . -type f ! -path '*/\.*' ! -path '*/node_modules/*' ! -path '*/vendor/*' | \
- awk -F. '{print $NF}' | sort | uniq -c | sort -rn | head -20
-
-# Line counts by language
-cloc . --json 2>/dev/null || tokei . || echo "Install cloc/tokei for detailed stats"
-
-# Large files (potential refactoring targets)
-find . -type f ! -path '*/\.*' -exec wc -l {} \; | sort -rn | head -20
-
-# TODO/FIXME/HACK comments (potential improvement areas)
-grep -r "TODO\|FIXME\|HACK\|XXX\|NOTE:" --include="*.f*" --include="*.ml*" --include="*.c" --include="*.h" --include="*.py" --include="*.js" . 2>/dev/null | wc -l
-grep -r "TODO\|FIXME\|HACK" --include="*.f*" --include="*.ml*" --include="*.c" --include="*.h" . 2>/dev/null | head -30
-```
-
-### 1.3 Research Project Documentation
-
-Read and understand key documentation:
-
-```bash
-cd "$REPO_DIR"
-
-# Read README
-if [ -f README.md ]; then
- head -100 README.md
-elif [ -f README ]; then
- head -100 README
-fi
-
-# Check for project website or docs
-if [ -d docs ]; then
- find docs -name "*.md" | head -10
-fi
-
-# Contributing guidelines
-if [ -f CONTRIBUTING.md ]; then
- head -50 CONTRIBUTING.md
-fi
-```
-
-## Phase 2: GitHub Actions Analysis
-
-### 2.1 Survey Existing Workflows
-
-Analyze all GitHub Actions workflows in detail:
-
-```bash
-# List all workflows
-gh api "repos/${{ inputs.repository }}/actions/workflows" --jq '.workflows[] | {
- name: .name,
- path: .path,
- state: .state,
- created_at: .created_at,
- updated_at: .updated_at
-}'
-
-# Clone if not already done
-cd "$REPO_DIR" || exit 1
-
-# Analyze workflow files
-find .github/workflows -name "*.yml" -o -name "*.yaml" 2>/dev/null
-
-for workflow in .github/workflows/*.{yml,yaml}; do
- if [ -f "$workflow" ]; then
- echo "=== Workflow: $workflow ==="
-
- # Extract triggers
- echo "Triggers:"
- grep -A 5 "^on:" "$workflow" || grep -A 5 "^'on':" "$workflow"
-
- # Extract jobs
- echo "Jobs:"
- grep "^ [a-zA-Z_-]*:" "$workflow" | grep -v "^ on:" | head -20
-
- # Check for complexity indicators
- echo "Complexity indicators:"
- grep -c "uses:" "$workflow" || echo "0"
- grep -c "run:" "$workflow" || echo "0"
- grep -c "if:" "$workflow" || echo "0"
-
- echo ""
- fi
-done
-```
-
-### 2.2 Workflow Run History and Patterns
-
-Analyze recent workflow runs to identify patterns:
-
-```bash
-# Recent workflow runs (last 30 days)
-gh api "repos/${{ inputs.repository }}/actions/runs?per_page=100&created=>=$(date -d '30 days ago' +%Y-%m-%d 2>/dev/null || date -v-30d +%Y-%m-%d)" --jq '.workflow_runs[] | {
- id: .id,
- name: .name,
- status: .status,
- conclusion: .conclusion,
- created_at: .created_at,
- run_number: .run_number
-}' > /tmp/workflow_runs.json
-
-# Success rate
-cat /tmp/workflow_runs.json | jq -s 'group_by(.name) | map({
- workflow: .[0].name,
- total: length,
- success: map(select(.conclusion == "success")) | length,
- failure: map(select(.conclusion == "failure")) | length,
- cancelled: map(select(.conclusion == "cancelled")) | length
-})'
-
-# Failed runs analysis
-cat /tmp/workflow_runs.json | jq -s 'map(select(.conclusion == "failure")) | group_by(.name) | map({
- workflow: .[0].name,
- failures: length
-}) | sort_by(.failures) | reverse'
-```
-
-### 2.3 Identify Workflow Inefficiencies
-
-Look for common issues in existing workflows:
-
-```bash
-cd "$REPO_DIR"
-
-# Long-running jobs (no caching)
-echo "Checking for caching usage:"
-grep -l "cache" .github/workflows/*.{yml,yaml} 2>/dev/null | wc -l
-echo "Workflows without cache:"
-find .github/workflows -name "*.yml" -o -name "*.yaml" | wc -l
-
-# Deprecated actions
-echo "Checking for deprecated actions:"
-grep "actions/checkout@v1\|actions/setup-node@v1\|actions/cache@v1" .github/workflows/*.{yml,yaml} 2>/dev/null
-
-# Missing continue-on-error for optional jobs
-echo "Jobs without continue-on-error (potential blockers):"
-grep -B 5 "run:" .github/workflows/*.{yml,yaml} 2>/dev/null | grep -c "continue-on-error" || echo "0"
-
-# Hardcoded secrets or tokens
-echo "Potential hardcoded secrets:"
-# Use bash variable construction to avoid triggering expression extraction
-EXPR_START='$'; EXPR_OPEN='{{'; grep -r "token\|password\|api_key" .github/workflows/*.{yml,yaml} 2>/dev/null | grep -v "${EXPR_START}${EXPR_OPEN}" | wc -l
-```
-
-## Phase 3: Issue History Analysis
-
-### 3.1 Issue Patterns and Trends
-
-Analyze issue history to identify recurring problems:
-
-```bash
-# Recent issues (last 90 days)
-gh api "repos/${{ inputs.repository }}/issues?state=all&per_page=100&since=$(date -d '90 days ago' +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || date -v-90d +%Y-%m-%dT%H:%M:%SZ)" --jq '.[] | {
- number: .number,
- title: .title,
- state: .state,
- labels: [.labels[].name],
- created_at: .created_at,
- closed_at: .closed_at,
- comments: .comments
-}' > /tmp/issues.json
-
-# Issue categories (by labels)
-cat /tmp/issues.json | jq -s 'map(.labels[]) | group_by(.) | map({label: .[0], count: length}) | sort_by(.count) | reverse'
-
-# Open vs closed ratio
-cat /tmp/issues.json | jq -s 'group_by(.state) | map({state: .[0].state, count: length})'
-
-# Issues with most comments (high engagement)
-cat /tmp/issues.json | jq -s 'sort_by(.comments) | reverse | .[0:10] | .[] | {number: .number, title: .title, comments: .comments}'
-
-# Common words in issue titles (identify patterns)
-cat /tmp/issues.json | jq -r '.[].title' | tr '[:upper:]' '[:lower:]' | tr ' ' '\n' | sort | uniq -c | sort -rn | head -30
-```
-
-### 3.2 Identify Automation Opportunities in Issues
-
-Look for issues that could be automated:
-
-```bash
-# Issues about CI/CD
-cat /tmp/issues.json | jq -s 'map(select(.title | test("ci|cd|build|test|deploy"; "i"))) | length'
-
-# Issues about documentation
-cat /tmp/issues.json | jq -s 'map(select(.title | test("doc|documentation|readme"; "i"))) | length'
-
-# Issues about dependencies/updates
-cat /tmp/issues.json | jq -s 'map(select(.title | test("update|upgrade|dependency|dependabot"; "i"))) | length'
-
-# Repetitive issues (same labels appearing frequently)
-cat /tmp/issues.json | jq -s 'map(select(.labels | length > 0)) | group_by(.labels | sort) | map({labels: .[0].labels, count: length}) | sort_by(.count) | reverse | .[0:10]'
-```
-
-## Phase 4: Identify Agentic Workflow Opportunities
-
-Based on the analysis, identify specific opportunities for agentic workflows:
-
-### 4.1 Daily Improver Opportunities
-
-Patterns that suggest daily/scheduled improvements:
-
-1. **Code Quality Monitoring**
- - High TODO/FIXME count → Daily code quality report workflow
- - Large files → Daily refactoring suggestions workflow
- - Test coverage gaps → Weekly test coverage improvement workflow
-
-2. **Documentation Maintenance**
- - Outdated documentation → Daily docs freshness checker
- - Missing API docs → Weekly API documentation generator
- - Broken links → Daily link checker and fixer
-
-3. **Dependency Management**
- - Outdated dependencies → Weekly dependency update analyzer
- - Security vulnerabilities → Daily security scan workflow
- - License compliance → Monthly license audit workflow
-
-4. **Issue Management**
- - Unlabeled issues → Auto-labeling workflow (on issue open)
- - Stale issues → Weekly stale issue classifier
- - Duplicate detection → On-demand duplicate issue finder
-
-5. **PR Automation**
- - Code review assistance → On PR open reviewer assignment
- - Test coverage reports → On PR synchronize coverage checker
- - Breaking change detection → On PR open breaking change analyzer
-
-### 4.2 Event-Driven Opportunities
-
-Patterns that suggest event-triggered workflows:
-
-1. **Issues**
- - Frequent bug reports → Auto-triage and label on issue creation
- - Feature requests → Feature request classifier
- - Support questions → Auto-response with resources
-
-2. **Pull Requests**
- - Complex PRs → Automated review checklist generator
- - Security-sensitive changes → Security review required marker
- - Documentation changes → Docs preview and validation
-
-3. **Releases**
- - Release notes generation from commits
- - Changelog automation
- - Version bump suggestions
-
-### 4.3 Repository-Specific Opportunities
-
-Based on the actual patterns found in the target repository, create custom recommendations.
-
-## Phase 5: Generate Comprehensive Report
-
-Create a detailed analysis report with actionable recommendations:
-
-### Report Structure
-
-```markdown
-# 🔍 Repository Audit & Agentic Workflow Opportunities Report
-
-**Repository**: ${{ inputs.repository }}
-**Analysis Date**: $(date +%Y-%m-%d)
-**Audit Type**: Comprehensive (code + workflows + issues + patterns)
-
-## 📋 Executive Summary
-
-[3-4 paragraphs summarizing the repository, current state, key findings, and top opportunities]
-
-**Key Metrics:**
-- **Repository Age**: [X] years
-- **Primary Language**: [Language]
-- **Active Contributors**: [N]
-- **Open Issues**: [N]
-- **GitHub Actions Workflows**: [N]
-- **Automation Opportunities Found**: [N]
-
----
-
-## 🏗️ Repository Overview
-
-
-Project Details
-
-### Project Information
-- **Name**: [Name]
-- **Description**: [Description]
-- **Stars**: [N] ⭐
-- **Forks**: [N] 🍴
-- **Language**: [Primary Language]
-- **Topics**: [List of topics]
-
-### Technology Stack
-[Languages and frameworks used]
-
-### Repository Structure
-```
-[Key directories and their purposes]
-```
-
-### Development Activity
-- **Recent Commits**: [N] in last 30 days
-- **Open Issues**: [N]
-- **Open Pull Requests**: [N]
-- **Active Contributors**: [N]
-
-
-
----
-
-## 🤖 GitHub Actions Analysis
-
-### Current Workflows
-
-| Workflow Name | Trigger | Purpose | Status |
-|---------------|---------|---------|--------|
-| [Name] | [on: push/pr/schedule] | [Purpose] | ✅/⚠️/❌ |
-
-### Workflow Health Assessment
-
-**Strengths:**
-- [List strengths in current automation]
-
-**Issues Found:**
-- [Issue 1: e.g., "No caching in build workflows - increasing execution time"]
-- [Issue 2: e.g., "Deprecated action versions (actions/checkout@v1)"]
-- [Issue 3: e.g., "Missing failure notifications"]
-
-**Metrics:**
-- **Total Workflows**: [N]
-- **Success Rate (30d)**: [X]%
-- **Average Execution Time**: [X] minutes
-- **Failed Runs (30d)**: [N]
-
----
-
-## 🎯 Agentic Workflow Opportunities
-
-### High Priority Opportunities
-
-#### 1. [Opportunity Name]
-
-**Type**: Daily Improver / Event-Driven / On-Demand
-**Priority**: High 🔴
-**Estimated Impact**: High
-**Implementation Effort**: Medium
-
-**Problem Statement:**
-[Describe the problem this workflow would solve]
-
-**Proposed Workflow:**
-- **Trigger**: [e.g., "schedule: daily", "on: issues: opened"]
-- **Actions**: [What the workflow would do]
-- **Tools Needed**: [e.g., "github, web-fetch, serena"]
-- **Safe Outputs**: [e.g., "create-issue, add-comment"]
-- **Expected Benefits**: [Quantified benefits if possible]
-
-**Implementation Sketch:**
-```yaml
----
-description: [Brief description]
-on:
- [trigger configuration]
-permissions:
- [minimal permissions]
-tools:
- [required tools]
-safe-outputs:
- [output configuration]
----
-
-[Agent prompt outline]
-```
-
-**Success Metrics:**
-- [Metric 1: e.g., "Reduce unlabeled issues from 30% to 5%"]
-- [Metric 2: e.g., "Save 2 hours/week on manual triage"]
-
----
-
-#### 2. [Opportunity Name]
-[Same structure as above]
-
----
-
-#### 3. [Opportunity Name]
-[Same structure as above]
-
----
-
-### Medium Priority Opportunities
-
-[Brief list of 3-5 medium priority opportunities with shorter descriptions]
-
-### Future Opportunities
-
-[List of 3-5 future opportunities for consideration]
-
----
-
-## 📊 Issue Pattern Analysis
-
-### Common Issue Categories
-
-| Category | Count (90d) | % of Total | Automation Potential |
-|----------|-------------|------------|---------------------|
-| [Bug] | [N] | [X]% | [High/Medium/Low] |
-| [Feature Request] | [N] | [X]% | [High/Medium/Low] |
-| [Documentation] | [N] | [X]% | [High/Medium/Low] |
-
-### Recurring Patterns
-
-**Pattern 1**: [Description]
-- **Frequency**: [N] occurrences
-- **Automation Opportunity**: [How to automate]
-
-**Pattern 2**: [Description]
-- **Frequency**: [N] occurrences
-- **Automation Opportunity**: [How to automate]
-
-### Issue Lifecycle Metrics
-
-- **Average Time to First Response**: [X] hours
-- **Average Time to Close**: [X] days
-- **Issues with >10 Comments**: [N] (high engagement topics)
-
----
-
-## 💻 Code Pattern Analysis
-
-### Code Quality Insights
-
-**Positive Findings:**
-- [Strength 1]
-- [Strength 2]
-
-**Improvement Areas:**
-- [Area 1: e.g., "153 TODO comments - opportunity for task tracking automation"]
-- [Area 2: e.g., "12 files >1000 lines - potential refactoring targets"]
-- [Area 3: e.g., "Test coverage gaps in core modules"]
-
-### Technical Debt Indicators
-
-| Indicator | Count | Severity | Automation Opportunity |
-|-----------|-------|----------|----------------------|
-| TODO comments | [N] | Medium | Daily TODO → Issue converter |
-| Large files (>500 LOC) | [N] | Medium | Weekly refactoring suggestions |
-| Duplicate code | [N] blocks | Low | Monthly code deduplication report |
-
----
-
-## 🚀 Implementation Roadmap
-
-### Phase 1: Quick Wins (Week 1-2)
-1. **[Workflow 1]** - [Why it's a quick win]
-2. **[Workflow 2]** - [Why it's a quick win]
-
-### Phase 2: High Impact (Week 3-6)
-1. **[Workflow 3]** - [Expected impact]
-2. **[Workflow 4]** - [Expected impact]
-
-### Phase 3: Long-term (Month 2-3)
-1. **[Workflow 5]** - [Strategic value]
-2. **[Workflow 6]** - [Strategic value]
-
----
-
-## 📈 Expected Impact
-
-### Quantitative Benefits
-
-- **Time Savings**: ~[X] hours/week freed from manual tasks
-- **Issue Triage Speed**: [X]% faster average response time
-- **Code Quality**: [X]% reduction in technical debt indicators
-- **Workflow Efficiency**: [X]% improvement in CI/CD success rate
-
-### Qualitative Benefits
-
-- Improved developer experience
-- Better issue management
-- Enhanced code quality
-- Reduced maintenance burden
-- Better community engagement
-
----
-
-## 🔄 Continuous Improvement
-
-### Monitoring & Metrics
-
-**Track these metrics after implementation:**
-1. Workflow success rates
-2. Time saved on manual tasks
-3. Issue response times
-4. Code quality metrics
-5. Community engagement metrics
-
-### Iteration Strategy
-
-1. Start with high-priority, low-effort workflows
-2. Monitor performance for 2 weeks
-3. Gather feedback from maintainers
-4. Iterate and improve
-5. Expand to medium-priority workflows
-
----
-
-## 📚 Repository-Specific Recommendations
-
-### Custom Insights for ${{ inputs.repository }}
-
-[Based on actual analysis, provide specific recommendations that are unique to this repository, not generic advice]
-
-**Language-Specific Opportunities:**
-[If repository uses F*, OCaml, etc., suggest language-specific tools and workflows]
-
-**Community Patterns:**
-[Based on issue/PR patterns, suggest community engagement workflows]
-
-**Project-Specific Automation:**
-[Based on build/test patterns, suggest project-specific automation]
-
----
-
-## 💾 Cache Memory Update
-
-[Document what was stored in cache for future analysis]
-
-**Stored Data:**
-- Repository metadata: `/tmp/gh-aw/cache-memory/repo-audits/${REPO_SLUG}.json`
-- Workflow patterns: `/tmp/gh-aw/cache-memory/repo-audits/${REPO_SLUG}_workflows.json`
-- Issue patterns: `/tmp/gh-aw/cache-memory/repo-audits/${REPO_SLUG}_issues.json`
-
-**Next Analysis:**
-- Recommended re-analysis: 30 days
-- Focus areas for next audit: [List]
-
----
-
-## 🎯 Next Steps
-
-### Immediate Actions
-
-1. **Review this report** with repository maintainers
-2. **Prioritize opportunities** based on team needs and capacity
-3. **Create workflow specifications** for top 3 priorities
-4. **Set up a pilot workflow** to validate approach
-
-### Getting Started
-
-To implement these workflows:
-1. Use the `gh aw` CLI to create workflow files
-2. Start with the implementation sketches provided
-3. Test with `workflow_dispatch` before enabling automatic triggers
-4. Monitor and iterate based on results
-
-### Resources
-
-- GitHub Agentic Workflows documentation: [Link]
-- Example workflows: `.github/workflows/` in gh-aw repository
-- MCP servers for tools: [Registry link]
-
----
-
-*Generated by Repository Audit & Agentic Workflow Opportunity Analyzer*
-*For questions or feedback, create an issue in the gh-aw repository*
-```
-
-## Phase 6: Update Cache Memory
-
-After generating the report, save analysis data for future reference:
-
-```bash
-# Save repository metadata
-REPO_SLUG=$(echo "${{ inputs.repository }}" | tr '/' '_')
-
-cat > "/tmp/gh-aw/cache-memory/repo-audits/${REPO_SLUG}.json" << EOF
-{
- "repository": "${{ inputs.repository }}",
- "analysis_date": "$(date +%Y-%m-%d)",
- "primary_language": "[detected language]",
- "workflow_count": [N],
- "open_issues": [N],
- "opportunities_found": [N],
- "high_priority_count": [N],
- "medium_priority_count": [N],
- "last_updated": "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
-}
-EOF
-
-echo "Analysis cached for future comparison"
-```
-
-## Success Criteria
-
-A successful audit run:
-- ✅ Clones and analyzes the target repository
-- ✅ Surveys all GitHub Actions workflows
-- ✅ Analyzes issue history and patterns
-- ✅ Identifies code patterns and technical debt
-- ✅ Generates 5-8 actionable workflow opportunities
-- ✅ Prioritizes opportunities by impact and effort
-- ✅ Provides implementation sketches for top 3 opportunities
-- ✅ Creates exactly one discussion with comprehensive report
-- ✅ Updates cache memory with analysis data
-- ✅ Includes repository-specific insights (not generic advice)
-
-## Important Guidelines
-
-### Thoroughness
-- **Deep Analysis**: Don't just skim - read documentation, understand the project
-- **Data-Driven**: Use actual metrics and patterns, not assumptions
-- **Specific**: Provide exact workflows, file paths, and code examples
-- **Actionable**: Every opportunity should have a clear implementation path
-
-### Creativity
-- **Think Beyond Standard Patterns**: Each repository is unique
-- **Consider Project Type**: Academic project? Open source tool? Framework?
-- **Community Patterns**: How do contributors interact? What pain points exist?
-- **Domain-Specific**: What automation makes sense for THIS domain?
-
-### Practicality
-- **Start Small**: Recommend quick wins first
-- **Clear ROI**: Explain the value of each workflow
-- **Realistic Scope**: Don't overwhelm with 50 opportunities
-- **Maintainable**: Suggest workflows that are easy to maintain
-
-### Report Quality
-- **Clear Structure**: Use the provided template consistently
-- **Visual Organization**: Use tables, lists, and emphasis effectively
-- **Context**: Explain WHY each opportunity matters
-- **Examples**: Provide concrete implementation sketches
-
-## Output Requirements
-
-Your output MUST:
-1. Create exactly one discussion with the comprehensive audit report
-2. Analyze actual data from the repository (not generic assumptions)
-3. Provide 5-8 prioritized workflow opportunities
-4. Include implementation sketches for top 3 opportunities
-5. Update cache memory with analysis results
-6. Follow the detailed report template structure
-7. Include repository-specific insights and recommendations
-
-Begin your repository audit analysis now!
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
index 3a8d6f0fa7..f0fe076e34 100644
--- a/.github/dependabot.yml
+++ b/.github/dependabot.yml
@@ -20,3 +20,7 @@ updates:
directory: /.github/workflows
schedule:
interval: weekly
+- package-ecosystem: gomod
+ directory: /.github/workflows
+ schedule:
+ interval: weekly
diff --git a/.github/workflows/daily-multi-device-docs-tester.lock.yml b/.github/workflows/daily-multi-device-docs-tester.lock.yml
index 3146dac49c..4d270fb16b 100644
--- a/.github/workflows/daily-multi-device-docs-tester.lock.yml
+++ b/.github/workflows/daily-multi-device-docs-tester.lock.yml
@@ -170,7 +170,7 @@ jobs:
const determineAutomaticLockdown = require('/opt/gh-aw/actions/determine_automatic_lockdown.cjs');
await determineAutomaticLockdown(github, context, core);
- name: Download container images
- run: bash /opt/gh-aw/actions/download_docker_images.sh ghcr.io/github/gh-aw-mcpg:v0.0.96 ghcr.io/github/github-mcp-server:v0.30.2 mcr.microsoft.com/playwright/mcp node:lts-alpine
+ run: bash /opt/gh-aw/actions/download_docker_images.sh ghcr.io/github/gh-aw-mcpg:v0.0.94 ghcr.io/github/github-mcp-server:v0.30.2 mcr.microsoft.com/playwright/mcp node:lts-alpine
- name: Write Safe Outputs Config
run: |
mkdir -p /opt/gh-aw/safeoutputs
@@ -452,7 +452,7 @@ jobs:
# Register API key as secret to mask it from logs
echo "::add-mask::${MCP_GATEWAY_API_KEY}"
export GH_AW_ENGINE="claude"
- export MCP_GATEWAY_DOCKER_COMMAND='docker run -i --rm --network host -v /var/run/docker.sock:/var/run/docker.sock -e MCP_GATEWAY_PORT -e MCP_GATEWAY_DOMAIN -e MCP_GATEWAY_API_KEY -e DEBUG -e MCP_GATEWAY_LOG_DIR -e GH_AW_MCP_LOG_DIR -e GH_AW_SAFE_OUTPUTS -e GH_AW_SAFE_OUTPUTS_CONFIG_PATH -e GH_AW_SAFE_OUTPUTS_TOOLS_PATH -e GH_AW_ASSETS_BRANCH -e GH_AW_ASSETS_MAX_SIZE_KB -e GH_AW_ASSETS_ALLOWED_EXTS -e DEFAULT_BRANCH -e GITHUB_MCP_SERVER_TOKEN -e GITHUB_MCP_LOCKDOWN -e GITHUB_REPOSITORY -e GITHUB_SERVER_URL -e GITHUB_SHA -e GITHUB_WORKSPACE -e GITHUB_TOKEN -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RUN_ATTEMPT -e GITHUB_JOB -e GITHUB_ACTION -e GITHUB_EVENT_NAME -e GITHUB_EVENT_PATH -e GITHUB_ACTOR -e GITHUB_ACTOR_ID -e GITHUB_TRIGGERING_ACTOR -e GITHUB_WORKFLOW -e GITHUB_WORKFLOW_REF -e GITHUB_WORKFLOW_SHA -e GITHUB_REF -e GITHUB_REF_NAME -e GITHUB_REF_TYPE -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GH_AW_SAFE_OUTPUTS_PORT -e GH_AW_SAFE_OUTPUTS_API_KEY -v /opt:/opt:ro -v /tmp:/tmp:rw -v '"${GITHUB_WORKSPACE}"':'"${GITHUB_WORKSPACE}"':rw ghcr.io/github/gh-aw-mcpg:v0.0.96'
+ export MCP_GATEWAY_DOCKER_COMMAND='docker run -i --rm --network host -v /var/run/docker.sock:/var/run/docker.sock -e MCP_GATEWAY_PORT -e MCP_GATEWAY_DOMAIN -e MCP_GATEWAY_API_KEY -e DEBUG -e MCP_GATEWAY_LOG_DIR -e GH_AW_MCP_LOG_DIR -e GH_AW_SAFE_OUTPUTS -e GH_AW_SAFE_OUTPUTS_CONFIG_PATH -e GH_AW_SAFE_OUTPUTS_TOOLS_PATH -e GH_AW_ASSETS_BRANCH -e GH_AW_ASSETS_MAX_SIZE_KB -e GH_AW_ASSETS_ALLOWED_EXTS -e DEFAULT_BRANCH -e GITHUB_MCP_SERVER_TOKEN -e GITHUB_MCP_LOCKDOWN -e GITHUB_REPOSITORY -e GITHUB_SERVER_URL -e GITHUB_SHA -e GITHUB_WORKSPACE -e GITHUB_TOKEN -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RUN_ATTEMPT -e GITHUB_JOB -e GITHUB_ACTION -e GITHUB_EVENT_NAME -e GITHUB_EVENT_PATH -e GITHUB_ACTOR -e GITHUB_ACTOR_ID -e GITHUB_TRIGGERING_ACTOR -e GITHUB_WORKFLOW -e GITHUB_WORKFLOW_REF -e GITHUB_WORKFLOW_SHA -e GITHUB_REF -e GITHUB_REF_NAME -e GITHUB_REF_TYPE -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GH_AW_SAFE_OUTPUTS_PORT -e GH_AW_SAFE_OUTPUTS_API_KEY -v /opt:/opt:ro -v /tmp:/tmp:rw -v '"${GITHUB_WORKSPACE}"':'"${GITHUB_WORKSPACE}"':rw ghcr.io/github/gh-aw-mcpg:v0.0.94'
cat << MCPCONFIG_EOF | bash /opt/gh-aw/actions/start_mcp_gateway.sh
{
diff --git a/.github/workflows/go.mod b/.github/workflows/go.mod
index b322d484db..a537eb2f9b 100644
--- a/.github/workflows/go.mod
+++ b/.github/workflows/go.mod
@@ -1,3 +1,5 @@
module github.com/github/gh-aw-workflows-deps
-
go 1.21
+
+require (
+)
diff --git a/.github/workflows/repo-audit-analyzer.lock.yml b/.github/workflows/repo-audit-analyzer.lock.yml
index c4e8674c44..9451584fbc 100644
--- a/.github/workflows/repo-audit-analyzer.lock.yml
+++ b/.github/workflows/repo-audit-analyzer.lock.yml
@@ -27,7 +27,7 @@
#
# frontmatter-hash: 53e8f611f290c904288a97423cdb9aa1b8655defdfd44d856397e8fb5e447e38
-name: "Repo Audit Analyzer"
+name: "Repository Audit & Agentic Workflow Opportunity Analyzer"
"on":
workflow_dispatch:
inputs:
@@ -42,7 +42,7 @@ permissions: {}
concurrency:
group: "gh-aw-${{ github.workflow }}"
-run-name: "Repo Audit Analyzer"
+run-name: "Repository Audit & Agentic Workflow Opportunity Analyzer"
jobs:
activation:
@@ -451,7 +451,7 @@ jobs:
model: process.env.GH_AW_MODEL_AGENT_COPILOT || "",
version: "",
agent_version: "0.0.400",
- workflow_name: "Repo Audit Analyzer",
+ workflow_name: "Repository Audit & Agentic Workflow Opportunity Analyzer",
experimental: false,
supports_tools_allowlist: true,
supports_http_transport: true,
@@ -907,7 +907,7 @@ jobs:
env:
GH_AW_AGENT_OUTPUT: ${{ env.GH_AW_AGENT_OUTPUT }}
GH_AW_NOOP_MAX: 1
- GH_AW_WORKFLOW_NAME: "Repo Audit Analyzer"
+ GH_AW_WORKFLOW_NAME: "Repository Audit & Agentic Workflow Opportunity Analyzer"
with:
github-token: ${{ secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
script: |
@@ -923,7 +923,7 @@ jobs:
GH_AW_MISSING_TOOL_CREATE_ISSUE: "true"
GH_AW_MISSING_TOOL_TITLE_PREFIX: "[missing tool]"
GH_AW_MISSING_TOOL_LABELS: "[\"cookie\"]"
- GH_AW_WORKFLOW_NAME: "Repo Audit Analyzer"
+ GH_AW_WORKFLOW_NAME: "Repository Audit & Agentic Workflow Opportunity Analyzer"
with:
github-token: ${{ secrets.GH_AW_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
script: |
@@ -936,7 +936,7 @@ jobs:
uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8.0.0
env:
GH_AW_AGENT_OUTPUT: ${{ env.GH_AW_AGENT_OUTPUT }}
- GH_AW_WORKFLOW_NAME: "Repo Audit Analyzer"
+ GH_AW_WORKFLOW_NAME: "Repository Audit & Agentic Workflow Opportunity Analyzer"
GH_AW_RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
GH_AW_AGENT_CONCLUSION: ${{ needs.agent.result }}
GH_AW_SECRET_VERIFICATION_RESULT: ${{ needs.agent.outputs.secret_verification_result }}
@@ -958,7 +958,7 @@ jobs:
GH_AW_COMMENT_ID: ${{ needs.activation.outputs.comment_id }}
GH_AW_COMMENT_REPO: ${{ needs.activation.outputs.comment_repo }}
GH_AW_RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
- GH_AW_WORKFLOW_NAME: "Repo Audit Analyzer"
+ GH_AW_WORKFLOW_NAME: "Repository Audit & Agentic Workflow Opportunity Analyzer"
GH_AW_AGENT_CONCLUSION: ${{ needs.agent.result }}
GH_AW_DETECTION_CONCLUSION: ${{ needs.detection.result }}
with:
@@ -1010,7 +1010,7 @@ jobs:
- name: Setup threat detection
uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8.0.0
env:
- WORKFLOW_NAME: "Repo Audit Analyzer"
+ WORKFLOW_NAME: "Repository Audit & Agentic Workflow Opportunity Analyzer"
WORKFLOW_DESCRIPTION: "Comprehensive repository audit to identify productivity improvement opportunities using agentic workflows"
HAS_PATCH: ${{ needs.agent.outputs.has_patch }}
with:
@@ -1089,7 +1089,7 @@ jobs:
env:
GH_AW_ENGINE_ID: "copilot"
GH_AW_WORKFLOW_ID: "repo-audit-analyzer"
- GH_AW_WORKFLOW_NAME: "Repo Audit Analyzer"
+ GH_AW_WORKFLOW_NAME: "Repository Audit & Agentic Workflow Opportunity Analyzer"
outputs:
create_discussion_error_count: ${{ steps.process_safe_outputs.outputs.create_discussion_error_count }}
create_discussion_errors: ${{ steps.process_safe_outputs.outputs.create_discussion_errors }}
diff --git a/.github/workflows/repo-audit-analyzer.md b/.github/workflows/repo-audit-analyzer.md
index 839715e9d3..c51e4b51f0 100644
--- a/.github/workflows/repo-audit-analyzer.md
+++ b/.github/workflows/repo-audit-analyzer.md
@@ -35,5 +35,740 @@ imports:
- shared/reporting.md
---
-
-{{#runtime-import agentics/repo-audit-analyzer.md}}
+# Repository Audit & Agentic Workflow Opportunity Analyzer
+
+You are a repository audit specialist that analyzes GitHub repositories to identify opportunities for productivity improvements using agentic workflows.
+
+## Mission
+
+Conduct a comprehensive audit of the target repository to discover patterns, inefficiencies, and opportunities that could be automated or improved with agentic workflows. Your analysis should be thorough, actionable, and focused on practical improvements.
+
+## Current Context
+
+- **Target Repository**: ${{ inputs.repository }}
+- **Analysis Date**: $(date +%Y-%m-%d)
+- **Cache Location**: `/tmp/gh-aw/cache-memory/repo-audits/`
+
+## Phase 0: Setup and Repository Discovery
+
+### 0.1 Load Historical Analysis
+
+Check if this repository has been analyzed before:
+
+```bash
+# Create cache directory if it doesn't exist
+mkdir -p /tmp/gh-aw/cache-memory/repo-audits/
+
+# Check for previous analysis
+REPO_SLUG=$(echo "${{ inputs.repository }}" | tr '/' '_')
+if [ -f "/tmp/gh-aw/cache-memory/repo-audits/${REPO_SLUG}.json" ]; then
+ echo "Found previous analysis:"
+ cat "/tmp/gh-aw/cache-memory/repo-audits/${REPO_SLUG}.json"
+fi
+```
+
+### 0.2 Gather Repository Metadata
+
+Use GitHub API to collect basic repository information:
+
+```bash
+# Repository info
+gh api "repos/${{ inputs.repository }}" --jq '{
+ name: .name,
+ full_name: .full_name,
+ description: .description,
+ language: .language,
+ stars: .stargazers_count,
+ forks: .forks_count,
+ open_issues: .open_issues_count,
+ created_at: .created_at,
+ updated_at: .updated_at,
+ size: .size,
+ default_branch: .default_branch,
+ topics: .topics,
+ has_issues: .has_issues,
+ has_discussions: .has_discussions,
+ has_wiki: .has_wiki
+}'
+
+# Contributors
+gh api "repos/${{ inputs.repository }}/contributors?per_page=10" --jq '.[] | {login: .login, contributions: .contributions}'
+
+# Languages
+gh api "repos/${{ inputs.repository }}/languages"
+```
+
+## Phase 1: Deep Research - Project Understanding
+
+### 1.1 Explore Repository Structure
+
+Analyze the repository structure to understand the project:
+
+```bash
+# Clone repository for deep analysis
+REPO_DIR="/tmp/repo-analysis"
+git clone "https://github.com/${{ inputs.repository }}.git" "$REPO_DIR" --depth 1
+
+cd "$REPO_DIR"
+
+# Directory structure
+tree -L 3 -d -I 'node_modules|.git|vendor' . || find . -type d -maxdepth 3 ! -path '*/\.*' ! -path '*/node_modules/*'
+
+# Key files
+ls -lh README* LICENSE* CONTRIBUTING* CODE_OF_CONDUCT* SECURITY* 2>/dev/null
+
+# Build and test files
+find . -maxdepth 2 -name "Makefile" -o -name "*.mk" -o -name "package.json" -o -name "go.mod" -o -name "requirements.txt" -o -name "Cargo.toml" -o -name "pom.xml" -o -name "build.gradle" -o -name ".fsproj" -o -name "*.sln"
+
+# Documentation
+find . -type d -name "docs" -o -name "documentation" -o -name "wiki"
+```
+
+### 1.2 Analyze Source Code Patterns
+
+Identify the primary programming languages and code patterns:
+
+```bash
+cd "$REPO_DIR"
+
+# Code statistics
+find . -type f ! -path '*/\.*' ! -path '*/node_modules/*' ! -path '*/vendor/*' | \
+ awk -F. '{print $NF}' | sort | uniq -c | sort -rn | head -20
+
+# Line counts by language
+cloc . --json 2>/dev/null || tokei . || echo "Install cloc/tokei for detailed stats"
+
+# Large files (potential refactoring targets)
+find . -type f ! -path '*/\.*' -exec wc -l {} \; | sort -rn | head -20
+
+# TODO/FIXME/HACK comments (potential improvement areas)
+grep -r "TODO\|FIXME\|HACK\|XXX\|NOTE:" --include="*.f*" --include="*.ml*" --include="*.c" --include="*.h" --include="*.py" --include="*.js" . 2>/dev/null | wc -l
+grep -r "TODO\|FIXME\|HACK" --include="*.f*" --include="*.ml*" --include="*.c" --include="*.h" . 2>/dev/null | head -30
+```
+
+### 1.3 Research Project Documentation
+
+Read and understand key documentation:
+
+```bash
+cd "$REPO_DIR"
+
+# Read README
+if [ -f README.md ]; then
+ head -100 README.md
+elif [ -f README ]; then
+ head -100 README
+fi
+
+# Check for project website or docs
+if [ -d docs ]; then
+ find docs -name "*.md" | head -10
+fi
+
+# Contributing guidelines
+if [ -f CONTRIBUTING.md ]; then
+ head -50 CONTRIBUTING.md
+fi
+```
+
+## Phase 2: GitHub Actions Analysis
+
+### 2.1 Survey Existing Workflows
+
+Analyze all GitHub Actions workflows in detail:
+
+```bash
+# List all workflows
+gh api "repos/${{ inputs.repository }}/actions/workflows" --jq '.workflows[] | {
+ name: .name,
+ path: .path,
+ state: .state,
+ created_at: .created_at,
+ updated_at: .updated_at
+}'
+
+# Clone if not already done
+cd "$REPO_DIR" || exit 1
+
+# Analyze workflow files
+find .github/workflows -name "*.yml" -o -name "*.yaml" 2>/dev/null
+
+for workflow in .github/workflows/*.{yml,yaml}; do
+ if [ -f "$workflow" ]; then
+ echo "=== Workflow: $workflow ==="
+
+ # Extract triggers
+ echo "Triggers:"
+ grep -A 5 "^on:" "$workflow" || grep -A 5 "^'on':" "$workflow"
+
+ # Extract jobs
+ echo "Jobs:"
+ grep "^ [a-zA-Z_-]*:" "$workflow" | grep -v "^ on:" | head -20
+
+ # Check for complexity indicators
+ echo "Complexity indicators:"
+ grep -c "uses:" "$workflow" || echo "0"
+ grep -c "run:" "$workflow" || echo "0"
+ grep -c "if:" "$workflow" || echo "0"
+
+ echo ""
+ fi
+done
+```
+
+### 2.2 Workflow Run History and Patterns
+
+Analyze recent workflow runs to identify patterns:
+
+```bash
+# Recent workflow runs (last 30 days)
+gh api "repos/${{ inputs.repository }}/actions/runs?per_page=100&created=>=$(date -d '30 days ago' +%Y-%m-%d 2>/dev/null || date -v-30d +%Y-%m-%d)" --jq '.workflow_runs[] | {
+ id: .id,
+ name: .name,
+ status: .status,
+ conclusion: .conclusion,
+ created_at: .created_at,
+ run_number: .run_number
+}' > /tmp/workflow_runs.json
+
+# Success rate
+cat /tmp/workflow_runs.json | jq -s 'group_by(.name) | map({
+ workflow: .[0].name,
+ total: length,
+ success: map(select(.conclusion == "success")) | length,
+ failure: map(select(.conclusion == "failure")) | length,
+ cancelled: map(select(.conclusion == "cancelled")) | length
+})'
+
+# Failed runs analysis
+cat /tmp/workflow_runs.json | jq -s 'map(select(.conclusion == "failure")) | group_by(.name) | map({
+ workflow: .[0].name,
+ failures: length
+}) | sort_by(.failures) | reverse'
+```
+
+### 2.3 Identify Workflow Inefficiencies
+
+Look for common issues in existing workflows:
+
+```bash
+cd "$REPO_DIR"
+
+# Long-running jobs (no caching)
+echo "Checking for caching usage:"
+grep -l "cache" .github/workflows/*.{yml,yaml} 2>/dev/null | wc -l
+echo "Workflows without cache:"
+find .github/workflows -name "*.yml" -o -name "*.yaml" | wc -l
+
+# Deprecated actions
+echo "Checking for deprecated actions:"
+grep "actions/checkout@v1\|actions/setup-node@v1\|actions/cache@v1" .github/workflows/*.{yml,yaml} 2>/dev/null
+
+# Missing continue-on-error for optional jobs
+echo "Jobs without continue-on-error (potential blockers):"
+grep -B 5 "run:" .github/workflows/*.{yml,yaml} 2>/dev/null | grep -c "continue-on-error" || echo "0"
+
+# Hardcoded secrets or tokens
+echo "Potential hardcoded secrets:"
+# Use bash variable construction to avoid triggering expression extraction
+EXPR_START='$'; EXPR_OPEN='{{'; grep -r "token\|password\|api_key" .github/workflows/*.{yml,yaml} 2>/dev/null | grep -v "${EXPR_START}${EXPR_OPEN}" | wc -l
+```
+
+## Phase 3: Issue History Analysis
+
+### 3.1 Issue Patterns and Trends
+
+Analyze issue history to identify recurring problems:
+
+```bash
+# Recent issues (last 90 days)
+gh api "repos/${{ inputs.repository }}/issues?state=all&per_page=100&since=$(date -d '90 days ago' +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || date -v-90d +%Y-%m-%dT%H:%M:%SZ)" --jq '.[] | {
+ number: .number,
+ title: .title,
+ state: .state,
+ labels: [.labels[].name],
+ created_at: .created_at,
+ closed_at: .closed_at,
+ comments: .comments
+}' > /tmp/issues.json
+
+# Issue categories (by labels)
+cat /tmp/issues.json | jq -s 'map(.labels[]) | group_by(.) | map({label: .[0], count: length}) | sort_by(.count) | reverse'
+
+# Open vs closed ratio
+cat /tmp/issues.json | jq -s 'group_by(.state) | map({state: .[0].state, count: length})'
+
+# Issues with most comments (high engagement)
+cat /tmp/issues.json | jq -s 'sort_by(.comments) | reverse | .[0:10] | .[] | {number: .number, title: .title, comments: .comments}'
+
+# Common words in issue titles (identify patterns)
+cat /tmp/issues.json | jq -r '.[].title' | tr '[:upper:]' '[:lower:]' | tr ' ' '\n' | sort | uniq -c | sort -rn | head -30
+```
+
+### 3.2 Identify Automation Opportunities in Issues
+
+Look for issues that could be automated:
+
+```bash
+# Issues about CI/CD
+cat /tmp/issues.json | jq -s 'map(select(.title | test("ci|cd|build|test|deploy"; "i"))) | length'
+
+# Issues about documentation
+cat /tmp/issues.json | jq -s 'map(select(.title | test("doc|documentation|readme"; "i"))) | length'
+
+# Issues about dependencies/updates
+cat /tmp/issues.json | jq -s 'map(select(.title | test("update|upgrade|dependency|dependabot"; "i"))) | length'
+
+# Repetitive issues (same labels appearing frequently)
+cat /tmp/issues.json | jq -s 'map(select(.labels | length > 0)) | group_by(.labels | sort) | map({labels: .[0].labels, count: length}) | sort_by(.count) | reverse | .[0:10]'
+```
+
+## Phase 4: Identify Agentic Workflow Opportunities
+
+Based on the analysis, identify specific opportunities for agentic workflows:
+
+### 4.1 Daily Improver Opportunities
+
+Patterns that suggest daily/scheduled improvements:
+
+1. **Code Quality Monitoring**
+ - High TODO/FIXME count → Daily code quality report workflow
+ - Large files → Daily refactoring suggestions workflow
+ - Test coverage gaps → Weekly test coverage improvement workflow
+
+2. **Documentation Maintenance**
+ - Outdated documentation → Daily docs freshness checker
+ - Missing API docs → Weekly API documentation generator
+ - Broken links → Daily link checker and fixer
+
+3. **Dependency Management**
+ - Outdated dependencies → Weekly dependency update analyzer
+ - Security vulnerabilities → Daily security scan workflow
+ - License compliance → Monthly license audit workflow
+
+4. **Issue Management**
+ - Unlabeled issues → Auto-labeling workflow (on issue open)
+ - Stale issues → Weekly stale issue classifier
+ - Duplicate detection → On-demand duplicate issue finder
+
+5. **PR Automation**
+ - Code review assistance → On PR open reviewer assignment
+ - Test coverage reports → On PR synchronize coverage checker
+ - Breaking change detection → On PR open breaking change analyzer
+
+### 4.2 Event-Driven Opportunities
+
+Patterns that suggest event-triggered workflows:
+
+1. **Issues**
+ - Frequent bug reports → Auto-triage and label on issue creation
+ - Feature requests → Feature request classifier
+ - Support questions → Auto-response with resources
+
+2. **Pull Requests**
+ - Complex PRs → Automated review checklist generator
+ - Security-sensitive changes → Security review required marker
+ - Documentation changes → Docs preview and validation
+
+3. **Releases**
+ - Release notes generation from commits
+ - Changelog automation
+ - Version bump suggestions
+
+### 4.3 Repository-Specific Opportunities
+
+Based on the actual patterns found in the target repository, create custom recommendations.
+
+## Phase 5: Generate Comprehensive Report
+
+Create a detailed analysis report with actionable recommendations:
+
+### Report Structure
+
+```markdown
+# 🔍 Repository Audit & Agentic Workflow Opportunities Report
+
+**Repository**: ${{ inputs.repository }}
+**Analysis Date**: $(date +%Y-%m-%d)
+**Audit Type**: Comprehensive (code + workflows + issues + patterns)
+
+## 📋 Executive Summary
+
+[3-4 paragraphs summarizing the repository, current state, key findings, and top opportunities]
+
+**Key Metrics:**
+- **Repository Age**: [X] years
+- **Primary Language**: [Language]
+- **Active Contributors**: [N]
+- **Open Issues**: [N]
+- **GitHub Actions Workflows**: [N]
+- **Automation Opportunities Found**: [N]
+
+---
+
+## 🏗️ Repository Overview
+
+
+Project Details
+
+### Project Information
+- **Name**: [Name]
+- **Description**: [Description]
+- **Stars**: [N] ⭐
+- **Forks**: [N] 🍴
+- **Language**: [Primary Language]
+- **Topics**: [List of topics]
+
+### Technology Stack
+[Languages and frameworks used]
+
+### Repository Structure
+```
+[Key directories and their purposes]
+```
+
+### Development Activity
+- **Recent Commits**: [N] in last 30 days
+- **Open Issues**: [N]
+- **Open Pull Requests**: [N]
+- **Active Contributors**: [N]
+
+
+
+---
+
+## 🤖 GitHub Actions Analysis
+
+### Current Workflows
+
+| Workflow Name | Trigger | Purpose | Status |
+|---------------|---------|---------|--------|
+| [Name] | [on: push/pr/schedule] | [Purpose] | ✅/⚠️/❌ |
+
+### Workflow Health Assessment
+
+**Strengths:**
+- [List strengths in current automation]
+
+**Issues Found:**
+- [Issue 1: e.g., "No caching in build workflows - increasing execution time"]
+- [Issue 2: e.g., "Deprecated action versions (actions/checkout@v1)"]
+- [Issue 3: e.g., "Missing failure notifications"]
+
+**Metrics:**
+- **Total Workflows**: [N]
+- **Success Rate (30d)**: [X]%
+- **Average Execution Time**: [X] minutes
+- **Failed Runs (30d)**: [N]
+
+---
+
+## 🎯 Agentic Workflow Opportunities
+
+### High Priority Opportunities
+
+#### 1. [Opportunity Name]
+
+**Type**: Daily Improver / Event-Driven / On-Demand
+**Priority**: High 🔴
+**Estimated Impact**: High
+**Implementation Effort**: Medium
+
+**Problem Statement:**
+[Describe the problem this workflow would solve]
+
+**Proposed Workflow:**
+- **Trigger**: [e.g., "schedule: daily", "on: issues: opened"]
+- **Actions**: [What the workflow would do]
+- **Tools Needed**: [e.g., "github, web-fetch, serena"]
+- **Safe Outputs**: [e.g., "create-issue, add-comment"]
+- **Expected Benefits**: [Quantified benefits if possible]
+
+**Implementation Sketch:**
+```yaml
+---
+description: [Brief description]
+on:
+ [trigger configuration]
+permissions:
+ [minimal permissions]
+tools:
+ [required tools]
+safe-outputs:
+ [output configuration]
+---
+
+[Agent prompt outline]
+```
+
+**Success Metrics:**
+- [Metric 1: e.g., "Reduce unlabeled issues from 30% to 5%"]
+- [Metric 2: e.g., "Save 2 hours/week on manual triage"]
+
+---
+
+#### 2. [Opportunity Name]
+[Same structure as above]
+
+---
+
+#### 3. [Opportunity Name]
+[Same structure as above]
+
+---
+
+### Medium Priority Opportunities
+
+[Brief list of 3-5 medium priority opportunities with shorter descriptions]
+
+### Future Opportunities
+
+[List of 3-5 future opportunities for consideration]
+
+---
+
+## 📊 Issue Pattern Analysis
+
+### Common Issue Categories
+
+| Category | Count (90d) | % of Total | Automation Potential |
+|----------|-------------|------------|---------------------|
+| [Bug] | [N] | [X]% | [High/Medium/Low] |
+| [Feature Request] | [N] | [X]% | [High/Medium/Low] |
+| [Documentation] | [N] | [X]% | [High/Medium/Low] |
+
+### Recurring Patterns
+
+**Pattern 1**: [Description]
+- **Frequency**: [N] occurrences
+- **Automation Opportunity**: [How to automate]
+
+**Pattern 2**: [Description]
+- **Frequency**: [N] occurrences
+- **Automation Opportunity**: [How to automate]
+
+### Issue Lifecycle Metrics
+
+- **Average Time to First Response**: [X] hours
+- **Average Time to Close**: [X] days
+- **Issues with >10 Comments**: [N] (high engagement topics)
+
+---
+
+## 💻 Code Pattern Analysis
+
+### Code Quality Insights
+
+**Positive Findings:**
+- [Strength 1]
+- [Strength 2]
+
+**Improvement Areas:**
+- [Area 1: e.g., "153 TODO comments - opportunity for task tracking automation"]
+- [Area 2: e.g., "12 files >1000 lines - potential refactoring targets"]
+- [Area 3: e.g., "Test coverage gaps in core modules"]
+
+### Technical Debt Indicators
+
+| Indicator | Count | Severity | Automation Opportunity |
+|-----------|-------|----------|----------------------|
+| TODO comments | [N] | Medium | Daily TODO → Issue converter |
+| Large files (>500 LOC) | [N] | Medium | Weekly refactoring suggestions |
+| Duplicate code | [N] blocks | Low | Monthly code deduplication report |
+
+---
+
+## 🚀 Implementation Roadmap
+
+### Phase 1: Quick Wins (Week 1-2)
+1. **[Workflow 1]** - [Why it's a quick win]
+2. **[Workflow 2]** - [Why it's a quick win]
+
+### Phase 2: High Impact (Week 3-6)
+1. **[Workflow 3]** - [Expected impact]
+2. **[Workflow 4]** - [Expected impact]
+
+### Phase 3: Long-term (Month 2-3)
+1. **[Workflow 5]** - [Strategic value]
+2. **[Workflow 6]** - [Strategic value]
+
+---
+
+## 📈 Expected Impact
+
+### Quantitative Benefits
+
+- **Time Savings**: ~[X] hours/week freed from manual tasks
+- **Issue Triage Speed**: [X]% faster average response time
+- **Code Quality**: [X]% reduction in technical debt indicators
+- **Workflow Efficiency**: [X]% improvement in CI/CD success rate
+
+### Qualitative Benefits
+
+- Improved developer experience
+- Better issue management
+- Enhanced code quality
+- Reduced maintenance burden
+- Better community engagement
+
+---
+
+## 🔄 Continuous Improvement
+
+### Monitoring & Metrics
+
+**Track these metrics after implementation:**
+1. Workflow success rates
+2. Time saved on manual tasks
+3. Issue response times
+4. Code quality metrics
+5. Community engagement metrics
+
+### Iteration Strategy
+
+1. Start with high-priority, low-effort workflows
+2. Monitor performance for 2 weeks
+3. Gather feedback from maintainers
+4. Iterate and improve
+5. Expand to medium-priority workflows
+
+---
+
+## 📚 Repository-Specific Recommendations
+
+### Custom Insights for ${{ inputs.repository }}
+
+[Based on actual analysis, provide specific recommendations that are unique to this repository, not generic advice]
+
+**Language-Specific Opportunities:**
+[If repository uses F*, OCaml, etc., suggest language-specific tools and workflows]
+
+**Community Patterns:**
+[Based on issue/PR patterns, suggest community engagement workflows]
+
+**Project-Specific Automation:**
+[Based on build/test patterns, suggest project-specific automation]
+
+---
+
+## 💾 Cache Memory Update
+
+[Document what was stored in cache for future analysis]
+
+**Stored Data:**
+- Repository metadata: `/tmp/gh-aw/cache-memory/repo-audits/${REPO_SLUG}.json`
+- Workflow patterns: `/tmp/gh-aw/cache-memory/repo-audits/${REPO_SLUG}_workflows.json`
+- Issue patterns: `/tmp/gh-aw/cache-memory/repo-audits/${REPO_SLUG}_issues.json`
+
+**Next Analysis:**
+- Recommended re-analysis: 30 days
+- Focus areas for next audit: [List]
+
+---
+
+## 🎯 Next Steps
+
+### Immediate Actions
+
+1. **Review this report** with repository maintainers
+2. **Prioritize opportunities** based on team needs and capacity
+3. **Create workflow specifications** for top 3 priorities
+4. **Set up a pilot workflow** to validate approach
+
+### Getting Started
+
+To implement these workflows:
+1. Use the `gh aw` CLI to create workflow files
+2. Start with the implementation sketches provided
+3. Test with `workflow_dispatch` before enabling automatic triggers
+4. Monitor and iterate based on results
+
+### Resources
+
+- GitHub Agentic Workflows documentation: [Link]
+- Example workflows: `.github/workflows/` in gh-aw repository
+- MCP servers for tools: [Registry link]
+
+---
+
+*Generated by Repository Audit & Agentic Workflow Opportunity Analyzer*
+*For questions or feedback, create an issue in the gh-aw repository*
+```
+
+## Phase 6: Update Cache Memory
+
+After generating the report, save analysis data for future reference:
+
+```bash
+# Save repository metadata
+REPO_SLUG=$(echo "${{ inputs.repository }}" | tr '/' '_')
+
+cat > "/tmp/gh-aw/cache-memory/repo-audits/${REPO_SLUG}.json" << EOF
+{
+ "repository": "${{ inputs.repository }}",
+ "analysis_date": "$(date +%Y-%m-%d)",
+ "primary_language": "[detected language]",
+ "workflow_count": [N],
+ "open_issues": [N],
+ "opportunities_found": [N],
+ "high_priority_count": [N],
+ "medium_priority_count": [N],
+ "last_updated": "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
+}
+EOF
+
+echo "Analysis cached for future comparison"
+```
+
+## Success Criteria
+
+A successful audit run:
+- ✅ Clones and analyzes the target repository
+- ✅ Surveys all GitHub Actions workflows
+- ✅ Analyzes issue history and patterns
+- ✅ Identifies code patterns and technical debt
+- ✅ Generates 5-8 actionable workflow opportunities
+- ✅ Prioritizes opportunities by impact and effort
+- ✅ Provides implementation sketches for top 3 opportunities
+- ✅ Creates exactly one discussion with comprehensive report
+- ✅ Updates cache memory with analysis data
+- ✅ Includes repository-specific insights (not generic advice)
+
+## Important Guidelines
+
+### Thoroughness
+- **Deep Analysis**: Don't just skim - read documentation, understand the project
+- **Data-Driven**: Use actual metrics and patterns, not assumptions
+- **Specific**: Provide exact workflows, file paths, and code examples
+- **Actionable**: Every opportunity should have a clear implementation path
+
+### Creativity
+- **Think Beyond Standard Patterns**: Each repository is unique
+- **Consider Project Type**: Academic project? Open source tool? Framework?
+- **Community Patterns**: How do contributors interact? What pain points exist?
+- **Domain-Specific**: What automation makes sense for THIS domain?
+
+### Practicality
+- **Start Small**: Recommend quick wins first
+- **Clear ROI**: Explain the value of each workflow
+- **Realistic Scope**: Don't overwhelm with 50 opportunities
+- **Maintainable**: Suggest workflows that are easy to maintain
+
+### Report Quality
+- **Clear Structure**: Use the provided template consistently
+- **Visual Organization**: Use tables, lists, and emphasis effectively
+- **Context**: Explain WHY each opportunity matters
+- **Examples**: Provide concrete implementation sketches
+
+## Output Requirements
+
+Your output MUST:
+1. Create exactly one discussion with the comprehensive audit report
+2. Analyze actual data from the repository (not generic assumptions)
+3. Provide 5-8 prioritized workflow opportunities
+4. Include implementation sketches for top 3 opportunities
+5. Update cache memory with analysis results
+6. Follow the detailed report template structure
+7. Include repository-specific insights and recommendations
+
+Begin your repository audit analysis now!
diff --git a/docs/src/content/docs/agent-factory-status.mdx b/docs/src/content/docs/agent-factory-status.mdx
index 3a854e0a58..45c775c568 100644
--- a/docs/src/content/docs/agent-factory-status.mdx
+++ b/docs/src/content/docs/agent-factory-status.mdx
@@ -113,7 +113,7 @@ These are experimental agentic workflows used by the GitHub Next team to learn,
| [Q](https://github.com/github/gh-aw/blob/main/.github/workflows/q.md) | copilot | [](https://github.com/github/gh-aw/actions/workflows/q.lock.yml) | - | `/q` |
| [Rebuild the documentation after making changes](https://github.com/github/gh-aw/blob/main/.github/workflows/technical-doc-writer.md) | copilot | [](https://github.com/github/gh-aw/actions/workflows/technical-doc-writer.lock.yml) | - | - |
| [Release](https://github.com/github/gh-aw/blob/main/.github/workflows/release.md) | copilot | [](https://github.com/github/gh-aw/actions/workflows/release.lock.yml) | - | - |
-| [Repo Audit Analyzer](https://github.com/github/gh-aw/blob/main/.github/workflows/repo-audit-analyzer.md) | copilot | [](https://github.com/github/gh-aw/actions/workflows/repo-audit-analyzer.lock.yml) | - | - |
+| [Repository Audit & Agentic Workflow Opportunity Analyzer](https://github.com/github/gh-aw/blob/main/.github/workflows/repo-audit-analyzer.md) | copilot | [](https://github.com/github/gh-aw/actions/workflows/repo-audit-analyzer.lock.yml) | - | - |
| [Repository Quality Improvement Agent](https://github.com/github/gh-aw/blob/main/.github/workflows/repository-quality-improver.md) | copilot | [](https://github.com/github/gh-aw/actions/workflows/repository-quality-improver.lock.yml) | `0 13 * * 1-5` | - |
| [Repository Tree Map Generator](https://github.com/github/gh-aw/blob/main/.github/workflows/repo-tree-map.md) | copilot | [](https://github.com/github/gh-aw/actions/workflows/repo-tree-map.lock.yml) | - | - |
| [Resource Summarizer Agent](https://github.com/github/gh-aw/blob/main/.github/workflows/pdf-summary.md) | copilot | [](https://github.com/github/gh-aw/actions/workflows/pdf-summary.lock.yml) | - | `/summarize` |
diff --git a/docs/src/content/docs/reference/frontmatter-full.md b/docs/src/content/docs/reference/frontmatter-full.md
index 664bd89f41..1387af92f1 100644
--- a/docs/src/content/docs/reference/frontmatter-full.md
+++ b/docs/src/content/docs/reference/frontmatter-full.md
@@ -1975,12 +1975,11 @@ safe-outputs:
# (optional)
description: "Description of the workflow"
- # Optional array of project custom fields to create up-front. Useful for project
- # setups that require a fixed set of fields.
+ # Optional array of project custom fields to create up-front.
# (optional)
field-definitions: []
# Array items:
- # The field name to create (e.g., 'status', 'tracker_id')
+ # The field name to create (e.g., 'status', 'priority')
name: "My Workflow"
# The GitHub Projects v2 custom field type
@@ -2024,8 +2023,8 @@ safe-outputs:
# (optional)
target-owner: "example-value"
- # Optional prefix for auto-generated project titles (default: 'Project'). When
- # the agent doesn't provide a title, the project title is auto-generated as
+ # Optional prefix for auto-generated project titles (default: 'Project'). When the
+ # agent doesn't provide a title, the project title is auto-generated as
# ': ' or ' #' based on the
# issue context.
# (optional)
@@ -2058,11 +2057,11 @@ safe-outputs:
description: "Description of the workflow"
# Optional array of project custom fields to create automatically after project
- # creation. Useful for projects that require a fixed set of fields.
+ # creation.
# (optional)
field-definitions: []
# Array items:
- # The field name to create (e.g., 'Tracker Id', 'Priority')
+ # The field name to create (e.g., 'Priority', 'Classification')
name: "My Workflow"
# The GitHub Projects v2 custom field type
@@ -2088,8 +2087,8 @@ safe-outputs:
# progress. Requires a Personal Access Token (PAT) or GitHub App token with
# Projects: Read+Write permission. The GITHUB_TOKEN cannot be used for Projects
# v2. Status updates are created on the specified project board and appear in the
- # Updates tab. Often used by scheduled workflows and orchestrator workflows to
- # post run summaries with progress, findings, and next steps.
+ # Updates tab. Typically used by orchestrators to post run summaries with
+ # progress, findings, and next steps.
create-project-status-update:
# Maximum number of status updates to create (default: 1). Typically 1 per
# orchestrator run.