emogies cleaning part 2

Author: taylorarndt

.github/ISSUE_TEMPLATE/challenge-hub.md

@@ -1,10 +1,8 @@
----
 name: "Challenge: {CHAPTER_NAME}"
 about: "Chapter {CHAPTER_NUM} Challenge - {CHALLENGE_SUMMARY}"
 title: "Chapter {CHAPTER_NUM}.{CHALLENGE_NUM}: {CHALLENGE_TITLE} (@{USERNAME})"
 labels: ["challenge", "challenge: {CHALLENGE_DIFFICULTY}", "skill: {SKILL_TAG}", "day: {DAY}"]
 assignees: ["{USERNAME}"]
----
 
 > [!WARNING]
 > This issue is part of the **GIT Going with GitHub** course.
@@ -16,21 +14,18 @@ assignees: ["{USERNAME}"]
 **Estimated Time:** {TIME_ESTIMATE}  
 **Skill Level:** {CHALLENGE_DIFFICULTY}  
 
----
 
 ## Challenge Overview
 
 {CHALLENGE_OVERVIEW}
 
 **All challenges in this chapter are linked to the [Challenge Hub](https://github.com/Community-Access/learning-room/blob/main/docs/CHALLENGES.md#chapter-{CHAPTER_NUM}-{ANCHOR_TEXT}) for full context and instructions.**
 
----
 
 ## Your Challenge: {CHALLENGE_TITLE}
 
 {CHALLENGE_BODY_FROM_HUB}
 
----
 
 ## What You Need to Do
 
@@ -39,7 +34,6 @@ assignees: ["{USERNAME}"]
 3. **Submit your work** - your PR should include proof of completion
 4. **See your issue close** automatically when your PR merges
 
----
 
 ## How to Submit
 
@@ -70,13 +64,11 @@ Then open a PR with:
 ### Step 5: Watch for Validation
 {VALIDATION_TEXT}
 
----
 
 ## Expected Outcomes
 
 {EXPECTED_OUTCOMES}
 
----
 
 ## If You Get Stuck
 
@@ -86,7 +78,6 @@ Then open a PR with:
 4. **Ask in Slack** - tag @facilitator with `#help` and your challenge number
 5. **Comment on this issue** - describe what's blocking you; facilitator will help
 
----
 
 ## Learning Moment
 

.github/ISSUE_TEMPLATES/ASSIGNMENT_ISSUE_TEMPLATE.md

@@ -2,7 +2,6 @@
 
 Use this template when pre-seeding issues for the Day 1 contribution sprint. Copy and modify for each student participant.
 
----
 
 ## Title
 `Fix: [specific problem] in [filename]`
@@ -45,7 +44,6 @@ See [Working with Issues](../../docs/04-working-with-issues.md) and the [Day 1 A
 - [Markdown Syntax Guide](../../docs/appendix-e-github-flavored-markdown.md)
 ```
 
----
 
 ## Pre-Seeded Issues to Create
 
@@ -62,7 +60,6 @@ Use this table as a checklist. Create one issue per row per student, customizing
 | `welcome.md` | [TODO] What merged PR means for profile | Sentence about GitHub profile/portfolio | `documentation`, `good-first-issue` | Medium |
 | `welcome.md` | Missing "Last reviewed" date | Date placeholder replaced with today's date | `documentation`, `good-first-issue` | Easy |
 
----
 
 ## Tips for Assigning Issues
 

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -46,6 +46,5 @@ If applicable, add a screenshot, GIF, or link to a demo showing your changes:
 
 [Add screenshot or video link here]
 
----
 
 **Have questions?** Ask in the comments below, or review [Working with Pull Requests](../../docs/05-working-with-pull-requests.md) for guidance.

.github/README.md

@@ -66,7 +66,6 @@ Automates peer review assignment and study group formation:
 **Configuration:** `.github/data/student-roster.json`  
 **Triggers:** PR opened/ready_for_review, manual dispatch
 
----
 
 ## File Structure
 
@@ -92,7 +91,6 @@ learning-room/
     └── GROUP_CHALLENGES.md            ← Collaborative exercises
 ```
 
----
 
 ## Quick Start
 
@@ -118,7 +116,6 @@ When you open a PR:
 
 **See:** [Automation Guide](../learning-room/AUTOMATION.md) for how to use the bot
 
----
 
 ## Configuration
 
@@ -167,7 +164,6 @@ Customize checks:
 
 Add new validation functions to `required` or `suggestions` arrays.
 
----
 
 ## Workflow Jobs Reference
 
@@ -230,7 +226,6 @@ Add new validation functions to `required` or `suggestions` arrays.
   - timezone_match: Group by timezone
 - Creates issue per group with collaboration guide
 
----
 
 ## Educational Philosophy
 
@@ -260,7 +255,6 @@ All automation components:
 - Work fully with screen readers
 - Mention screen reader considerations in guidance
 
----
 
 ## Monitoring & Troubleshooting
 
@@ -288,7 +282,6 @@ All automation components:
 
 **See:** [Implementation Guide - Troubleshooting](docs/IMPLEMENTATION_GUIDE.md#step-7-troubleshooting)
 
----
 
 ## Success Metrics
 
@@ -312,7 +305,6 @@ Track these to evaluate automation impact:
 - Number of PRs requiring facilitator intervention
 - Student satisfaction with automation
 
----
 
 ## Customization Examples
 
@@ -366,7 +358,6 @@ Edit `.github/data/challenge-progression.json`:
 }
 ```
 
----
 
 ## Documentation Map
 
@@ -382,7 +373,6 @@ Edit `.github/data/challenge-progression.json`:
 - [Workflow Files](workflows/) - Automation source code
 - [Data Files](data/) - Configuration (roster, progression)
 
----
 
 ## Contributing to Automation
 
@@ -400,7 +390,6 @@ Found a bug? Have a suggestion?
 - Custom grouping strategies
 - Additional validation checks
 
----
 
 ## Version History
 
@@ -418,7 +407,6 @@ Found a bug? Have a suggestion?
 - Advanced analytics and visualizations
 - Custom achievement builder UI
 
----
 
 ## Acknowledgments
 
@@ -432,7 +420,6 @@ This automation system was designed with these principles:
 
 Built for the Open Source Assistive Technology Hackathon workshop.
 
----
 
 **Questions?** Open an issue or reach out to workshop facilitators!
 

.github/agents/analytics.agent.md

@@ -1,10 +1,8 @@
----
 name: analytics
 description: Contribution velocity, review turnaround, code hotspots, and workload distribution across your repositories
 tools:
   - githubRepo
   - fetch
----
 
 You are a team analytics agent for open source maintainers and contributors. You surface patterns in contribution data that are difficult to see by manually reading GitHub Insights - and you present them in a format navigable by screen reader.
 

.github/agents/daily-briefing.agent.md

@@ -1,10 +1,8 @@
----
 name: daily-briefing
 description: Morning situation report - sweeps your repositories and surfaces what needs your attention today
 tools:
   - githubRepo
   - fetch
----
 
 You are a morning briefing agent for GitHub contributors who use assistive technology. Your job is to synthesize activity across repositories into a clear, structured, screen-reader-friendly briefing.
 

.github/agents/insiders-a11y-tracker.agent.md

@@ -1,10 +1,8 @@
----
 name: insiders-a11y-tracker
 description: Monitor accessibility-sensitive changes across repositories - WCAG/ARIA references, heading hierarchy, link quality, and keyboard navigation patterns
 tools:
   - githubRepo
   - fetch
----
 
 You are an accessibility change monitoring agent. You analyze recent commits and pull requests for changes that affect the accessibility of documentation, interfaces, or workflows - and you report findings before they are merged or published.
 

.github/agents/issue-tracker.agent.md

@@ -1,10 +1,8 @@
----
 name: issue-tracker
 description: Find, prioritize, triage, and draft responses to issues across your repositories
 tools:
   - githubRepo
   - fetch
----
 
 You are an issue management agent for open source contributors who use assistive technology. You help users navigate large issue backlogs, identify duplicates, find good first issues, and draft replies - without requiring them to manually scroll through hundreds of issues.
 
@@ -61,9 +59,7 @@ When asked to draft a reply to an issue:
 ```
 ## Draft Reply - Issue #[number]: [title]
 
----
 [draft text]
----
 
 This is a draft. Review, edit, and post it yourself. Your name goes on it.
 ```

.github/agents/pr-review.agent.md

@@ -1,10 +1,8 @@
----
 name: pr-review
 description: Generate structured review documentation for pull requests - change maps, risk summary, and suggested inline comments
 tools:
   - githubRepo
   - fetch
----
 
 You are a pull request review assistant for open source contributors who use assistive technology. You produce structured review documents that give a reviewer a complete starting point - not a finished review. The reviewer reads your output, edits it, adds context you cannot have, and posts it under their own name.
 

.github/agents/template-builder.agent.md

@@ -1,8 +1,6 @@
----
 name: Template Builder
 description: Interactive guided assistant for creating GitHub issue templates with VS Code Ask Questions integration
 topics: ["github", "issue-templates", "form-fields", "yaml", "accessibility"]
----
 
 # Template Builder Agent
 
@@ -39,7 +37,6 @@ A magical interactive agent that guides you through building GitHub issue templa
 
 **Agent outputs:** Complete YAML template ready to paste
 
----
 
 ## Template Builder Guide: Step-by-Step
 
@@ -61,7 +58,6 @@ title: "[TAG] "
 labels: ["label1", "label2"]
 ```
 
----
 
 ### Phase 2: Build Form Fields Interactively
 
@@ -98,7 +94,6 @@ The agent walks through adding fields one-by-one:
       required: true
 ```
 
----
 
 ### Phase 3: Generate Complete Template
 
@@ -120,7 +115,6 @@ Once all fields are entered, the agent:
    - How to edit it later
    - How to add it to the template chooser via config.yml
 
----
 
 ## Pre-Built Workflow: Guided Accessibility Template
 
@@ -144,7 +138,6 @@ The agent skips to Phase 2 but pre-populates it with accessibility-specific fiel
 
 Output: Production-ready accessibility bug template you can immediately use.
 
----
 
 ## Advanced: Customize the Template Builder
 
@@ -156,7 +149,6 @@ The Template Builder agent itself can be extended. Students in the workshop can:
 4. **Export to markdown** → Generate Markdown templates in addition to YAML
 5. **Template sharing** → Generate a code block to share with other projects
 
----
 
 ## Integration with Accessibility Agents
 
@@ -172,7 +164,6 @@ The Template Builder works alongside the five core agents:
 
 **Together:** The five agents automate workflow; the Template Builder automates the infrastructure that makes workflows possible.
 
----
 
 ## Day 2 Amplifier: From Manual to Magical
 
@@ -181,7 +172,6 @@ The Template Builder works alongside the five core agents:
 | Learn to identify accessibility issues in code review | Learn to design templates that prevent those issues | Use Template Builder to generate templates interactively | Agent automates the entire cycle |
 | (Chapter 14) | (Chapter 15) | (Chapter 16) | (Capstone) |
 
----
 
 ## Hands-On Exercise: Build Your Own Template Builder
 
@@ -217,7 +207,6 @@ Collect anonymous templates built by workshop participants:
 3. List your template (name, description, field count) in `COMMUNITY_TEMPLATES.md`
 4. Other participants can reference or fork your template
 
----
 
 ## Technical Details: VS Code Ask Questions Integration
 
@@ -228,10 +217,10 @@ The Template Builder uses VS Code's Ask Questions feature to create an interacti
 Agent asks (via Ask Questions UI):
 - Template name?
   [Input field with placeholder "e.g., Bug Report"]
-  
+
 - What is this template for?
   [Text area with prompt text]
-  
+
 Accept / Cancel buttons below
 ```
 
@@ -267,7 +256,6 @@ When the user clicks "Copy to Clipboard", the agent provides instructions:
 4. Paste the YAML
 5. Save and commit
 
----
 
 ## Troubleshooting & Tips
 
@@ -298,7 +286,6 @@ This agent creates GitHub issue templates, but the same pattern works for:
 - Discussion templates
 - GitHub Forms on custom websites
 
----
 
 ## Related Resources
 
@@ -307,6 +294,5 @@ This agent creates GitHub issue templates, but the same pattern works for:
 - [Chapter 14: Accessible Code Review](../docs/14-accessible-code-review.md) - Learn what accessibility issues to prevent via templates
 - [YAML Field Types Reference](../docs/15-issue-templates.md#6-yaml-form-based-templates) - Deep-dive on every field type
 
----
 
 *This agent makes template creation magical: go from idea to production-ready YAML in seconds. Use it for your repositories, share templates with teammates, and extend it for your specific workflows.*