Fix typos and add Sub-Issue Closer workflow

[github-actions]

This PR addresses both Phase 1 (consistency checks) and Phase 2 (workflow discovery) of the Daily Repo Goal Achiever task.

Phase 1: Consistency Fixes

Fixed typos and grammar issues found during documentation review:

Issues Fixed

1. Typo in workflows/daily-team-status.md (line 3)

   • Fixed: "This workflow created daily team status reporter" → "This workflow is a daily team status reporter"

2. Spelling in workflows/daily-qa.md and docs/daily-qa.md**

   • Fixed: "adhoc" → "ad hoc" (proper spelling of Latin phrase)
   • Updated heading from "Daily Adhoc QA" → "Daily Ad hoc QA"

3. Duplicate step numbering in workflows/pr-fix.md (lines 45-47)

   • Fixed: Steps numbered 4, 4, 5 → 4, 5, 6

4. Grammar in workflows/pr-fix.md (line 51)

   • Fixed: "...coding standards fixing any..." → "...coding standards and fix any..."

Phase 2: Workflow Discovery - Sub-Issue Closer

Added a new general-purpose workflow from Peli's Agent Factory: Sub-Issue Closer

Source

• Original: gh-aw/.github/workflows/sub-issue-closer.md
• Repository: https://github.com/github/gh-aw

Why This Workflow is Valuable

Perfect for General Use:

• ✅ No language dependencies (works for any tech stack)
• ✅ No framework dependencies
• ✅ Works for ANY repository using GitHub Issues with sub-issues
• ✅ Uses only standard GitHub APIs
• ✅ Simple, focused, practical scope
• ✅ Universally applicable automation pattern

Business Value:

• Reduces Manual Overhead: Eliminates need to manually close parent issues after completing all sub-tasks
• Maintains Clean Issue Tracker: Automatically keeps issue list organized
• Recursive Processing: Handles multi-level issue hierarchies intelligently
• Transparent Operations: Adds clear comments explaining closures
• Conservative Approach: Only closes when absolutely certain

What It Does

1. Scans all open parent issues in the repository
2. Checks 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

Example Use Case

When you have an issue hierarchy like:

Issue #10: "Major Feature" (OPEN)
├─ Issue #11: "Backend" (OPEN)
│  ├─ Issue #12: "API" (CLOSED)
│  └─ Issue #13: "DB" (CLOSED)
└─ Issue #14: "Frontend" (CLOSED)

The workflow will:

1. Detect Issue Product Management & Design Team #11 is 100% complete → Close #11
2. Check Issue Add Coordination & Planning Team agents for Agile project management #10's sub-issues → All closed
3. Close Issue Add Coordination & Planning Team agents for Agile project management #10 automatically with explanatory comment

Generalization Changes

To make this workflow suitable for the general-purpose agentics collection:

Removed:

• Shared imports (shared/mood.md)
• strict: true mode (not in base agentics patterns)
• gh-aw-specific references

Changed:

• Schedule: Kept as daily for simplicity
• Safe outputs: Added user-friendly messages
• Documentation: Enhanced with clearer general-purpose guidance
• Tools: Simplified to bash: true (standard pattern)

Kept:

• Core recursive closure logic
• GitHub issues API usage
• Conservative closure approach
• Transparent comment system
• Maximum 20 issues per run safety limit

Files Added

• workflows/sub-issue-closer.md - The workflow definition
• docs/sub-issue-closer.md - User-facing documentation
• README.md - Added entry in Triage Workflows section

All files follow the established patterns and style of existing agentics workflows.

AI generated by Daily Repo Goal Achiever