lightspeedwp · ashleyshaw · Nov 12, 2025 · Nov 12, 2025 · Nov 12, 2025 · Nov 12, 2025
@@ -1,124 +1,9 @@
----
-description: "Organized saved replies for consistent GitHub interactions across LightSpeedWP"
-version: "v1.0"
-last_updated: "2025-10-24"
-maintainer: "LightSpeed Engineering"
-tags: ["saved-replies", "communication", "automation", "community"]
----
+# Saved Replies (develop)
 
-# 💬 Saved Replies Directory
+Use these replies to accelerate triage. Do **not** hard-code label names; use placeholders:
 
-![Communication Badge](https://img.shields.io/badge/communication-standardized-brightgreen?style=flat-square)
-![Automation Badge](https://img.shields.io/badge/automation-ready-blue?style=flat-square)
+- `{issue_type}` → resolved to one of `type:*`
+- `{label:scope/docs}` → canonical label from `.github/automation/labels.yml`
 
-This directory contains standardized saved replies for consistent and professional GitHub interactions across all LightSpeedWP repositories.
-
-## 📁 Directory Structure
-
-### 🏘️ Community Replies (`community/`)
-
-- `code-of-conduct.md` - Code of conduct reminders and guidance
-- `contribution-thanks.md` - Thanking contributors and community members
-- `guidelines.md` - Community guideline references and explanations
-- `legal.md` - Legal and licensing related responses
-- `welcome.md` - Welcome messages for new contributors
-
-### 🐛 Issue Replies (`issues/`)
-
-- `a11y-acknowledge.md` - Accessibility issue acknowledgments
-- `area-routing.md` - Routing issues to appropriate areas/teams
-- `blockers.md` - Addressing blocking issues and dependencies
-- `bug-reports.md` - Bug report guidance and follow-up
-- `documentation.md` - Documentation requests and guidance
-- `duplicate.md` - Handling duplicate issues
-- `epic-tracking.md` - Epic and large feature tracking
-- `feature-requests.md` - Feature request processing
-- `good-first-issue.md` - Identifying good first issues for newcomers
-- `inactive-issue.md` - Handling inactive or stale issues
-- `label-clarification.md` - Explaining label meanings and usage
-- `missing-info.md` - Requesting additional information
-- `needs-reproduction.md` - Requesting bug reproduction steps
-- `security-acknowledge.md` - Security issue acknowledgments
-- `support.md` - Support request handling
-- `triage.md` - Issue triage and classification
-- `wontfix.md` - Issues that won't be fixed with explanations
-
-### 🔀 Pull Request Replies (`pull-requests/`)
-
-- `ai-assist.md` - AI assistance and Copilot guidance
-- `area-labeling.md` - PR area labeling explanations
-- `awaiting-author.md` - Waiting for author response
-- `branch-naming.md` - Branch naming convention guidance
-- `changelog-required.md` - Changelog requirements
-- `code-review.md` - Code review feedback and guidance
-- `conflicts.md` - Merge conflict resolution
-- `dependency-update.md` - Dependency update procedures
-- `documentation-pr.md` - Documentation PR guidelines
-- `merge-discipline.md` - Merge discipline and procedures
-- `needs-qa.md` - QA requirements and procedures
-- `performance.md` - Performance considerations
-- `ready-for-review.md` - PR ready for review notifications
-- `security.md` - Security-related PR guidance
-- `testing.md` - Testing requirements and guidance
-
-### 🔧 Technical Replies (`technical/`)
-
-- `api-integration.md` - API integration guidance
-- `code-style.md` - Code style and formatting guidance
-- `configuration.md` - Configuration and setup help
-- `dependencies.md` - Dependency management guidance
-- `environment-config.md` - Environment configuration help
-- `missing-tests.md` - Test coverage requirements
-- `performance.md` - Performance optimization guidance
-- `security.md` - Security best practices
-
-### 🔄 Workflow Replies (`workflow/`)
-
-- `automation.md` - Automation and workflow explanations
-- `branch-management.md` - Branch management procedures
-- `changelog-versioning.md` - Changelog and versioning guidance
-- `cicd-failures.md` - CI/CD failure explanations
-- `deployment.md` - Deployment procedures and guidance
-- `labeling.md` - Labeling system explanations
-- `permissions-secrets.md` - Permissions and secrets management
-- `project-sync.md` - Project synchronization procedures
-- `release-management.md` - Release management procedures
-- `workflow-failure.md` - Workflow failure troubleshooting
-
-## 🤖 Automation Integration
-
-Saved replies integrate with:
-
-- **[Saved Replies Prompt](../prompts/saved-replies.prompt.md)** - AI-powered reply suggestions
-- **[Issue Management Agents](../agents/README.md#issue-management)** - Automated issue responses
-- **[PR Automation](../agents/reviewer.agent.md)** - Automated PR feedback
-- **[Community Management](../AUTOMATION_GOVERNANCE.md)** - Community interaction automation
-
-## 📚 Related Documentation
-
-- [**Main Saved Replies Index**](../SAVED_REPLIES.md) - Complete saved replies documentation
-- [**Automation Governance**](../AUTOMATION_GOVERNANCE.md) - Communication automation standards
-- [**Issue Labels**](../ISSUE_LABELS.md) - Label-based response triggers
-- [**PR Labels**](../PR_LABELS.md) - PR-based response automation
-
-## 💡 Usage Guidelines
-
-1. **Consistency**: Use saved replies to maintain consistent messaging tone
-2. **Personalization**: Customize replies while maintaining core messaging
-3. **Context**: Choose the most appropriate reply for the specific situation
-4. **Automation**: Many replies are automatically suggested by AI agents
-5. **Updates**: Keep replies current with project changes and policies
-
-## 🔗 Cross-References
-
-- **Issue Templates**: Work with [issue templates](../ISSUE_TEMPLATE/README.md) for complete workflows
-- **PR Templates**: Complement [PR templates](../PULL_REQUEST_TEMPLATE/README.md) for comprehensive communication
-- **Chatmodes**: Enhanced by [communication chatmodes](../chatmodes/README.md)
-
----
-
-_This directory ensures consistent, professional communication across the LightSpeedWP organization. See [Communication Standards](../AUTOMATION_GOVERNANCE.md#communication) for complete guidelines._
-
----
-
-<!-- RANDOM FOOTER: 💬 Clear communication, stronger community! -->
+**Note:** Placeholders (e.g., `{issue_type}`, `{label:scope/docs}`) are automatically resolved by the repository's automation scripts during issue triage. The main resolution logic is implemented in the scripts under `.github/automation/`, which substitute these placeholders with the appropriate label names or values as defined in `.github/automation/labels.yml`.
+Keep replies DRY and short. Link to docs on the **develop** branch.
@@ -0,0 +1,40 @@
+#!/usr/bin/env node
+/**
+ * Writes a Markdown summary of the latest labeling run.
+ * TODO: wire to agent telemetry once available.
+ */
+const fs = require('fs');
+
+const data = {
+  timestamp: new Date().toISOString(),
+  totals: {
+    issues_processed: 0,
+    prs_processed: 0,
+    discussions_processed: 0,
+    labels_added: 0,
+    labels_removed: 0,
+    unknown_labels: 0,
+    alias_hits: 0
+  }
+  // TODO: read from agent runtime cache/JSON once implemented
+};
+
+const md = `# Labeling Report
+
+- Timestamp: ${data.timestamp}
+- Processed: issues=${data.totals.issues_processed}, prs=${data.totals.prs_processed}, discussions=${data.totals.discussions_processed}
+- Labels: added=${data.totals.labels_added}, removed=${data.totals.labels_removed}
+- Quality: unknown_labels=${data.totals.unknown_labels}, alias_hits=${data.totals.alias_hits}
+
+\`\`\`mermaid
+pie
+  title Labels by Source
+  "Issues" : ${data.totals.issues_processed}
+  "PRs" : ${data.totals.prs_processed}
+  "Discussions" : ${data.totals.discussions_processed}
+\`\`\`
+
+> NOTE: Replace counters with real telemetry once exposed by labeling.agent.js.
+`;
+
+process.stdout.write(md);