Daily Repo Goal Achiever: Fix typos and add Sub-Issue Closer workflow

actions-user · github-actions[bot] · commit 9e651bae65ae · 2026-02-13T17:02:26.000Z
diff --git a/README.md b/README.md
@@ -7,6 +7,7 @@ A sample family of reusable [GitHub Agentic Workflows](https://github.github.com
 ### Triage Workflows
 
 - [🏷️ Issue Triage](docs/issue-triage.md) - Triage issues and pull requests
+- [🔒 Sub-Issue Closer](docs/sub-issue-closer.md) - Automatically close parent issues when all sub-issues are complete
 
 ## Fault Analysis Workflows
 
diff --git a/docs/daily-qa.md b/docs/daily-qa.md
@@ -1,8 +1,8 @@
-# 🔍 Daily Adhoc QA
+# 🔍 Daily Ad hoc QA
 
 > For an overview of all available workflows, see the [main README](../README.md).
 
-The [daily Adhoc QA workflow](../workflows/daily-qa.md?plain=1) will perform adhoc quality assurance tasks in the repository, such as following the instructions in the README.md, tutorials and walkthroughs to check that the code builds and runs, and that the getting started process is simple and works well. You can edit and configure the workflow to describe more tasks. 
+The [daily Ad hoc QA workflow](../workflows/daily-qa.md?plain=1) will perform ad hoc quality assurance tasks in the repository, such as following the instructions in the README.md, tutorials and walkthroughs to check that the code builds and runs, and that the getting started process is simple and works well. You can edit and configure the workflow to describe more tasks. 
 
 ## Installation
 
diff --git a/docs/sub-issue-closer.md b/docs/sub-issue-closer.md
@@ -0,0 +1,92 @@
+# 🔒 Sub-Issue Closer
+
+> For an overview of all available workflows, see the [main README](../README.md).
+
+The [Sub-Issue Closer workflow](../workflows/sub-issue-closer.md?plain=1) automatically closes parent issues when all their sub-issues are 100% complete. This helps keep your issue tracker organized and reduces manual maintenance overhead when working with issue hierarchies.
+
+## What It Does
+
+1. Scans all open parent issues in the repository
+2. Checks the completion status of all sub-issues
+3. Recursively closes parent issues when all sub-issues are closed
+4. Adds explanatory comments to closed issues
+5. Provides a summary report of actions taken
+
+## Why It's Useful
+
+- **Reduces Manual Overhead**: No need to manually close parent issues after completing all sub-tasks
+- **Maintains Clean Issue Tracker**: Automatically keeps your issue list organized
+- **Recursive Processing**: Handles multi-level issue hierarchies intelligently
+- **Transparent Operations**: Adds clear comments explaining why issues were closed
+- **Conservative Approach**: Only closes when absolutely certain all sub-issues are complete
+
+## Installation
+
+```bash
+# Install the 'gh aw' extension
+gh extensions install github/gh-aw
+
+# Add the workflow
+gh aw add githubnext/agentics/sub-issue-closer
+
+# Compile to generate the GitHub Actions workflow
+gh aw compile
+```
+
+## Customization
+
+Edit `.github/workflows/sub-issue-closer.md` to adjust:
+
+- **Schedule**: Change from `daily` to a specific cron schedule
+- **Limits**: Modify `max: 20` to process more or fewer issues per run
+- **Timeout**: Adjust `timeout-minutes` based on your repository size
+- **Comment format**: Customize the closure comment template
+
+## How It Works
+
+The workflow uses GitHub's issue tracking relationships to identify parent issues and their sub-issues. It processes the issue hierarchy bottom-up, ensuring that sub-issues are evaluated before their parents. This enables recursive closure up the tree as each level reaches 100% completion.
+
+### Example Scenario
+
+You have this issue hierarchy:
+
+```
+Issue #10: "Major Feature Release" (OPEN)
+├─ Issue #11: "Backend changes" (OPEN)
+│  ├─ Issue #12: "API updates" (CLOSED)
+│  └─ Issue #13: "Database migration" (CLOSED)
+└─ Issue #14: "Frontend changes" (CLOSED)
+```
+
+When you close Issue #13 (the last sub-issue of #11), the workflow will:
+1. Detect Issue #11 is now 100% complete → Close #11
+2. Check if Issue #10's sub-issues are complete → Detect #14 (closed) and #11 (now closed)
+3. Close Issue #10 since all its sub-issues are complete
+
+## Safe Outputs
+
+The workflow uses these safe output actions:
+
+- **update-issue**: Closes parent issues (max 20 per run)
+- **add-comment**: Adds explanatory comments (max 20 per run)
+
+All actions are logged and visible in the workflow run output.
+
+## Permissions
+
+Requires these permissions:
+- `contents: read` - To access repository structure
+- `issues: read` - To query issue relationships
+
+## Best Practices
+
+1. **Use clear issue hierarchies**: Structure issues with explicit parent-child relationships
+2. **Review closure comments**: Check the automated comments to ensure correct operation
+3. **Start with manual testing**: Run via workflow_dispatch first to observe behavior
+4. **Adjust limits as needed**: Increase max values if you have large issue hierarchies
+5. **Combine with event-driven workflows**: Consider adding a complementary workflow that runs when individual issues close
+
+## Related Workflows
+
+- [Issue Triage](issue-triage.md) - Automated issue categorization and labeling
+- [Daily Plan](daily-plan.md) - Update planning issues for team coordination
diff --git a/workflows/daily-qa.md b/workflows/daily-qa.md
@@ -1,6 +1,6 @@
 ---
 description: |
-  This workflow performs adhoc quality assurance by validating project health daily.
+  This workflow performs ad hoc quality assurance by validating project health daily.
   Checks that code builds and runs, tests pass, documentation is clear, and code
   is well-structured. Creates discussions for findings and can submit draft PRs
   with improvements. Provides continuous quality monitoring throughout development.
diff --git a/workflows/daily-team-status.md b/workflows/daily-team-status.md
@@ -1,6 +1,6 @@
 ---
 description: |
-  This workflow created daily team status reporter creating upbeat activity summaries.
+  This workflow is a daily team status reporter creating upbeat activity summaries.
   Gathers recent repository activity (issues, PRs, discussions, releases, code changes)
   and generates engaging GitHub issues with productivity insights, community
   highlights, and project recommendations. Uses a positive, encouraging tone with
diff --git a/workflows/pr-fix.md b/workflows/pr-fix.md
@@ -44,11 +44,11 @@ You are an AI assistant specialized in fixing pull requests with failing CI chec
 
 4. Formulate a plan to follow the instructions. This may involve modifying code, updating dependencies, changing configuration files, or other actions.
 
-4. Implement the changes needed to follow the instructions.
+5. Implement the changes needed to follow the instructions.
 
 5. Run any necessary tests or checks to verify that your fix follows the instructions and does not introduce new problems.
 
-6. Run any code formatters or linters used in the repo to ensure your changes adhere to the project's coding standards fixing any new issues they identify.
+6. Run any code formatters or linters used in the repo to ensure your changes adhere to the project's coding standards and fix any new issues they identify.
 
 7. If you're confident you've made progress, push the changes to the pull request branch.
 
diff --git a/workflows/sub-issue-closer.md b/workflows/sub-issue-closer.md
@@ -0,0 +1,144 @@
+---
+description: Scheduled workflow that recursively closes parent issues when all sub-issues are 100% complete
+name: Sub-Issue Closer
+on:
+  schedule: daily
+  workflow_dispatch:
+permissions:
+  contents: read
+  issues: read
+engine: copilot
+timeout-minutes: 15
+tools:
+  github:
+    toolsets:
+      - issues
+  bash: true
+safe-outputs:
+  update-issue:
+    status:
+    target: "*"
+    max: 20
+  add-comment:
+    target: "*"
+    max: 20
+  messages:
+    run-started: "🔒 Starting Sub-Issue Closer... [{workflow_name}]({run_url}) is checking for completed parent issues"
+    run-success: "✅ Sub-Issue Closer complete! [{workflow_name}]({run_url}) has processed all parent issues."
+    run-failure: "❌ Sub-Issue Closer failed! [{workflow_name}]({run_url}) {status}. Some issues may not be processed."
+---
+
+# Sub-Issue Closer 🔒
+
+You are an intelligent agent that automatically closes parent issues when all their sub-issues are 100% complete.
+
+## Task
+
+Recursively process GitHub issues in repository **${{ github.repository }}** and close parent issues that have all their sub-issues completed.
+
+## Process
+
+### Step 1: Find Open Parent Issues
+
+Use the GitHub tools to search for open issues that have sub-issues. Look for:
+- Issues with state = "OPEN"
+- Issues that have tracked issues (sub-issues)
+- Issues that appear to be tracking/parent issues based on their structure
+
+You can use the `search_issues` tool to find issues with sub-issues, or use `list_issues` to get all open issues and filter those with sub-issues.
+
+### Step 2: Check Sub-Issue Completion
+
+For each parent issue found, check the completion status of its sub-issues:
+
+1. Get the sub-issues for the parent issue using the GitHub API
+2. Check if ALL sub-issues are in state "CLOSED"
+3. Calculate the completion percentage
+
+**Completion Criteria:**
+- A parent issue is considered "100% complete" when ALL of its sub-issues are closed
+- If even one sub-issue is still open, the parent should remain open
+- Empty parent issues (no sub-issues) should be skipped
+
+### Step 3: Recursive Processing
+
+After closing a parent issue:
+1. Check if that issue itself is a sub-issue of another parent
+2. If it has a parent issue, check that parent's completion status
+3. Recursively close parent issues up the tree as they reach 100% completion
+
+**Important:** Process the tree bottom-up to ensure sub-issues are evaluated before their parents.
+
+### Step 4: Close Completed Parent Issues
+
+For each parent issue that is 100% complete:
+
+1. **Close the issue** using the `update_issue` safe output tool
+2. **Add a comment** explaining the closure using the `add_comment` safe output tool
+
+Example comment body:
+```
+🎉 **Automatically closed by Sub-Issue Closer**
+
+All sub-issues have been completed. This parent issue is now closed automatically.
+
+**Sub-issues status:** X/X closed (100%)
+```
+
+### Step 5: Report Summary
+
+At the end of processing, provide a summary of:
+- Total parent issues analyzed
+- Issues closed in this run
+- Issues that remain open (with reason: incomplete sub-issues)
+- Any errors or issues that couldn't be processed
+
+## Constraints
+
+- Maximum 20 issues closed per run (configured in safe-outputs)
+- Maximum 20 comments added per run
+- Only close issues when you are ABSOLUTELY certain all sub-issues are closed
+- Skip issues that don't have sub-issues
+- Only process open parent issues
+- Be conservative: when in doubt, don't close
+
+## Example Output Format
+
+During processing, maintain clear logging:
+
+```
+🔍 Analyzing parent issues...
+
+📋 Issue #42: "Feature: Add dark mode"
+   State: OPEN
+   Sub-issues: 5 total
+   - #43: "Design dark mode colors" [CLOSED]
+   - #44: "Implement dark mode toggle" [CLOSED]
+   - #45: "Add dark mode to settings" [CLOSED]
+   - #46: "Test dark mode" [CLOSED]
+   - #47: "Document dark mode" [CLOSED]
+   Status: 5/5 closed (100%)
+   ✅ All sub-issues complete - CLOSING
+
+📋 Issue #50: "Feature: User authentication"
+   State: OPEN
+   Sub-issues: 3 total
+   - #51: "Add login page" [CLOSED]
+   - #52: "Add logout functionality" [OPEN]
+   - #53: "Add password reset" [CLOSED]
+   Status: 2/3 closed (67%)
+   ⏸️  Incomplete - keeping open
+
+✅ Summary:
+   - Parent issues analyzed: 2
+   - Issues closed: 1
+   - Issues remaining open: 1
+```
+
+## Important Notes
+
+- This is a scheduled workflow that runs daily
+- Use the GitHub tools to query issues and their relationships
+- Be careful with recursive processing to avoid infinite loops
+- Always verify the completion status before closing an issue
+- Add clear, informative comments when closing issues for transparency
