lightspeedwp · ashleyshaw · May 28, 2026 · May 28, 2026 · May 28, 2026 · May 28, 2026
@@ -2,9 +2,9 @@
 file_type: "documentation"
 title: "Issue Templates Directory"
 description: "Standardized issue templates for the LightSpeedWP organization"
-version: "v1.2"
+version: "v1.1"
 created_date: "2025-10-20"
-last_updated: "2026-05-28"
+last_updated: "2025-12-04"
 author: "LightSpeed Team"
 maintainer: "Ash Shaw"
 owners: ["lightspeedwp/maintainers"]
@@ -41,7 +41,7 @@ Get started with LightSpeedWP issue templates in three steps:
    - Select the appropriate template for your issue type (bug, feature, documentation, etc.)
    - Follow the instructions in the template to submit your issue
 
-For advanced usage, see the [Issue Template Index](./README.md) and individual template specs for configuration and automation options.
+For advanced usage, see the [Issue Template Index](./ISSUE_TEMPLATE/README.md) and individual template specs for configuration and automation options.
 
 ## 🗂️ Issue Template Workflow
 
@@ -84,10 +84,10 @@ The issue templates in this directory are automatically synchronized across all
 
 These templates integrate with:
 
-- **[Issue Types](../../docs/ISSUE_TYPES.md)** - Canonical issue type definitions
-- **[Issue Labels](../../docs/ISSUE_LABELS.md)** - Automated labeling system
-- **[Automation Governance](../../docs/AUTOMATION_GOVERNANCE.md)** - Agent-driven workflows
-- **[Branching Strategy](../../docs/BRANCHING_STRATEGY.md)** - Branch naming conventions
+- **[Issue Types](../ISSUE_TYPES.md)** - Canonical issue type definitions
+- **[Issue Labels](../ISSUE_LABELS.md)** - Automated labeling system
+- **[Automation Governance](../AUTOMATION_GOVERNANCE.md)** - Agent-driven workflows
+- **[Branching Strategy](../BRANCHING_STRATEGY.md)** - Branch naming conventions
 
 ## 🤖 Automation Features
 
@@ -115,14 +115,3 @@ These templates integrate with:
 *This directory is part of the LightSpeedWP automation ecosystem. See [Automation Governance](../../docs/AUTOMATION_GOVERNANCE.md) for complete automation standards.*
 
 ---
-
-<!-- RANDOM FOOTER: 🚀 Consistent templates, efficient workflows! -->
-
-*Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team*
-[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile)
-
-*Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team*
-[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile)
-
-*Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team*
-[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile)
@@ -79,8 +79,3 @@ These templates integrate with:
 *This directory is part of the LightSpeedWP automation ecosystem. See [Automation Governance](../../docs/AUTOMATION_GOVERNANCE.md) for complete automation standards.*
 
 ---
-
-<!-- RANDOM FOOTER: 🔀 Streamlined PRs, seamless integration! -->
-
-*Maintained with ❤️ by the 🚀 LightSpeedWP Automation Team*
-[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile)
@@ -2,15 +2,14 @@
 file_type: "documentation"
 title: "LightSpeed .github Community Health Repository"
 description: "Central hub for all shared GitHub templates, Copilot instructions, workflow automation, labeling systems, and community health files across the LightSpeed WordPress organisation"
-version: "3.2"
+version: "3.1"
 created_date: "2025-01-15"
-last_updated: "2026-05-28"
+last_updated: "2025-12-04"
 authors: ["LightSpeed Team"]
 maintainer: "LightSpeed Team"
 license: "GPL-3.0"
 domain: "governance"
 stability: "stable"
-status: "active"
 owners:
   - LightSpeed Team
 tags:
@@ -21,6 +20,35 @@ tags:
   - workflows
   - labeling
   - ai
+references:
+  - path: ./custom-instructions.md
+    description: Custom instructions for AI agents
+  - path: ./agents/agent.md
+    description: Main agents index
+  - path: ./prompts/prompts.md
+    description: Prompts index
+  - path: ../AGENTS.md
+    description: Organization-wide agents documentation
+  - path: ../docs/AUTOMATION_GOVERNANCE.md
+    description: Automation governance policies
+  - path: ./labels.yml
+    description: Label definitions
+  - path: ./labeler.yml
+    description: Labeler configuration
+  - path: ./issue-types.yml
+    description: Issue type definitions
+  - path: ./instructions/coding-standards.instructions.md
+    description: Coding standards instructions
+  - path: ./instructions/linting.instructions.md
+    description: Linting standards index
+  - path: ./instructions/tests.instructions.md
+    description: Testing standards index
+  - path: ./workflows/README.md
+    description: Workflows directory index
+  - path: ../CONTRIBUTING.md
+    description: Contribution guidelines
+  - path: ../docs/README.md
+    description: Documentation hub
 ---
 
 # 🏛️ LightSpeed Organisation .github Community Health Repository
@@ -449,12 +477,12 @@ Have questions, feedback, or want to propose an idea? Visit our [GitHub Discussi
 For all contributors, please reference these key guidelines and indexes:
 
 - [LightSpeed General Copilot Instructions](https://github.com/lightspeedwp/.github/blob/HEAD/.github/custom-instructions.md)
-- [Coding Standards](https://github.com/lightspeedwp/.github/blob/HEAD/instructions/coding-standards.instructions.md)
-- [HTML Templates](https://github.com/lightspeedwp/.github/blob/HEAD/.github/instructions/plugin-structure.instructions.md)
-- [Pattern Development](https://github.com/lightspeedwp/.github/blob/HEAD/.github/instructions/plugin-structure.instructions.md)
-- [PHP Block Instructions](https://github.com/lightspeedwp/.github/blob/HEAD/.github/instructions/plugin-structure.instructions.md)
-- [Theme JSON](https://github.com/lightspeedwp/.github/blob/HEAD/.github/instructions/plugin-structure.instructions.md)
-- When generating a summary for pull requests, use this [pull request template](https://github.com/lightspeedwp/.github/blob/HEAD/.github/pull_request_template.md).
+- [Coding Standards](https://github.com/lightspeedwp/.github/blob/HEAD/.github/instructions/coding-standards.instructions.md)
+- [HTML Templates](https://github.com/lightspeedwp/.github/blob/HEAD/.github/instructions/block-theme/html-template.instructions.md)
+- [Pattern Development](https://github.com/lightspeedwp/.github/blob/HEAD/.github/instructions/block-theme/pattern-development.instructions.md)
+- [PHP Block Instructions](https://github.com/lightspeedwp/.github/blob/HEAD/.github/instructions/block-theme/php-block.instructions.md)
+- [Theme JSON](https://github.com/lightspeedwp/.github/blob/HEAD/.github/instructions/block-theme/theme-json.instructions.md)
+- When generating a summary for pull requests, use this [pull request template](https://github.com/lightspeedwp/.github/blob/HEAD/.github/PULL_REQUEST_TEMPLATE.md).
 
 ---
 
@@ -547,21 +575,9 @@ This repository and all its contents are licensed under the GNU General Public L
 
 ## 🔧 Development Standards
 
-- [💻 Coding Standards](../instructions/coding-standards.instructions.md) - Unified development guidelines
-- [🎨 Linting Instructions](../instructions/linting.instructions.md) - Code quality and formatting
-- [🏗️ Pattern Development](./instructions/plugin-structure.instructions.md) - WordPress block patterns
-- [🌐 HTML Templates](./instructions/plugin-structure.instructions.md) - Semantic markup standards
+- [💻 Coding Standards](./instructions/coding-standards.instructions.md) - Unified development guidelines
+- [🎨 Linting Instructions](./instructions/linting.instructions.md) - Code quality and formatting
+- [🏗️ Pattern Development](./instructions/block-theme/pattern-development.instructions.md) - WordPress block patterns
+- [🌐 HTML Templates](./instructions/block-theme/html-template.instructions.md) - Semantic markup standards
 
 ---
-
-**🏛️ This directory is managed by the LightSpeed team. All organizational GitHub templates, automation, and AI resources are maintained here.**
-
-**❓ Questions?** [Open an issue](https://github.com/lightspeedwp/.github/issues/new), start a [Discussion](https://github.com/orgs/lightspeedwp/discussions), or contact [support@lightspeedwp.agency](mailto:support@lightspeedwp.agency)
-
-*Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit!*
-
-*Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit!*
-[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors)
-
-*Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit!*
-[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors)
@@ -104,117 +104,3 @@ Located in [`.github/SAVED_REPLIES/technical/`](./SAVED_REPLIES/technical/)
 | [api-integration.md](./SAVED_REPLIES/technical/api-integration.md) | API support/troubleshooting |
 
 ---
-
-## Usage Guidelines
-
-### When to Use Saved Replies
-
-- **Consistent Messaging**: When you need to communicate standard processes or policies
-- **Time Efficiency**: For frequently asked questions or common scenarios
-- **Quality Assurance**: To ensure complete and accurate information in responses
-- **Team Coordination**: When multiple team members handle similar issues
-
-### Customization Guidelines
-
-While saved replies provide a foundation, always:
-
-1. **Personalize the greeting** with the contributor's username
-2. **Reference specific details** from the issue or PR content
-3. **Add context-specific information** when relevant
-4. **Maintain professional and helpful tone** throughout
-5. **Include actionable next steps** for the contributor
-
-### Example Usage
-
-Instead of using a saved reply verbatim:
-
-```markdown
-Thank you for reporting this issue. We need more information to reproduce the problem.
-```
-
-Customize it for the specific case:
-
-```markdown
-Hi @username, thank you for reporting this deployment issue with the WordPress automation script.
-
-To help us reproduce the problem you're experiencing, could you please provide:
-
-- The specific script version you're using
-- Your target environment configuration
-- The complete error output from the logs
-- Steps you followed before encountering the issue
-
-This information will help us identify the root cause and provide a solution more quickly.
-```
-
-## Quality Standards
-
-All saved replies must:
-
-- **Follow LightSpeed WP tone and style guidelines**
-- **Provide clear, actionable guidance**
-- **Include relevant links to documentation or resources**
-- **Be technically accurate and up-to-date**
-- **Demonstrate empathy and professionalism**
-- **Offer specific next steps for resolution**
-
-## Maintenance and Updates
-
-### Regular Review Process
-
-- **Monthly Review**: Update replies based on new processes, tools, or standards
-- **Feedback Integration**: Incorporate team feedback and real-world usage patterns
-- **Link Validation**: Ensure all referenced documentation and resources remain accessible
-- **Template Optimization**: Refine templates based on effectiveness and user feedback
-
-### Contributing New Replies
-
-To add new saved replies:
-
-1. **Identify the need** based on frequent, similar responses required
-2. **Draft the reply** following established patterns and quality standards
-3. **Review with team** to ensure accuracy and appropriateness
-4. **Add to appropriate category** with clear naming and documentation
-5. **Update this index** to reference the new reply
-
-### Version Control
-
-- All saved replies are version controlled in the repository
-- Changes should be made via pull requests with appropriate review
-- Major updates should be communicated to the team
-- Historical versions are maintained for reference
-
-## Integration with GitHub
-
-### GitHub Saved Replies Feature
-
-These replies can be:
-
-- **Imported into GitHub's saved replies feature** for quick access
-- **Referenced in issue and PR templates** for consistency
-- **Used in automation workflows** for standardized responses
-- **Shared across team members** for unified communication
-
-### Automation Integration
-
-Saved replies integrate with:
-
-- **Issue labeling automation** for triggered responses
-- **PR review workflows** for standard feedback patterns
-- **Community management bots** for automatic responses
-- **Support ticket routing** for consistent first responses
-
-## Analytics and Improvement
-
-### Usage Tracking
-
-Monitor saved reply effectiveness through:
-
-- **Response time improvement** when using templates
-- **Issue resolution rates** with standard responses
-- **Contributor satisfaction** feedback and surveys
-- **Team efficiency** metrics and feedback
-
-### Continuous Improvement
-
-## Regular analysis helps identify
@@ -8,15 +8,3 @@ labels:
 references:
   - "../../CODE_OF_CONDUCT.md"
 ---
-
-# Code of Conduct Saved Reply
-
-Hi @username,
-
-Thank you for your message regarding our community standards.
-
-- We follow the [Contributor Covenant v2.1 Code of Conduct](../../CODE_OF_CONDUCT.md) for all LightSpeedWP projects.
-- If you experience or witness behavior that violates our standards, please report it to <conduct@lightspeedwp.agency> or the listed project maintainer.
-- All reports are confidential and reviewed promptly.
-
-We are committed to a safe, respectful, and inclusive community.
@@ -11,18 +11,3 @@ references:
   - "../../CODE_OF_CONDUCT.md"
   - "../../instructions/coding-standards.instructions.md"
 ---
-
-# Contribution Guidelines Saved Reply
-
-Hi @username,
-
-Thank you for your interest in contributing!
-
-**Before you start:**
-
-- Please read our [Contribution Guidelines](../../CONTRIBUTING.md)
-- Follow our [Coding Standards](../../instructions/coding-standards.instructions.md)
-- Respect our [Code of Conduct](../../CODE_OF_CONDUCT.md)
-- Use the correct issue and PR templates for your contribution type
-
-Following these steps ensures a smooth review process and helps us keep the project high-quality and welcoming to all.
@@ -9,15 +9,3 @@ references:
   - "../../LICENSE"
   - "../../CONTRIBUTING.md"
 ---
-
-# License and Legal Saved Reply
-
-Hi @username,
-
-Thank you for your question regarding licensing or legal compliance.
-
-- This project is licensed under the GNU General Public License v3.0. See the [LICENSE](../../LICENSE) file for full details.
-- For questions about contributions, copyright, or legal compliance, refer to our [Contribution Guidelines](../../CONTRIBUTING.md).
-- If you need further clarification or have specific legal needs, please contact our maintainers directly.
-
-We appreciate your diligence in ensuring legal compliance!
@@ -13,19 +13,3 @@ references:
   - "../../instructions/coding-standards.instructions.md"
   - "../../instructions/block-theme/pattern-development.instructions.md"
 ---
-
-# Welcome to LightSpeedWP
-
-Hi @username,
-
-Welcome to the LightSpeedWP community! 🎉
-
-**To get started:**
-
-- Review our [Contribution Guidelines](../../CONTRIBUTING.md)
-- Follow our [Code of Conduct](../../CODE_OF_CONDUCT.md) to foster a positive, inclusive environment
-- Explore [Coding Standards](../../instructions/coding-standards.instructions.md) and [Pattern Development](../../instructions/block-theme/pattern-development.instructions.md)
-
-If you have questions or want to claim a good first issue, just comment or tag a maintainer.
-
-Thank you for helping us build better WordPress solutions!
@@ -8,28 +8,3 @@ references:
   - "../ISSUE_LABELS.md"
   - "../ISSUE_TYPES.md"
 ---
-
-# Accessibility (A11y) Issue Acknowledgement Saved Replies
-
-## Accessibility Review Process
-
-**Use case**: For issues classified as **Accessibility (A11y)** via the Issue Type field, confirming review and triage.
-
-```markdown
-Hi @username,
-
-Thank you for raising this accessibility (A11y) issue. Inclusive, accessible experiences are important to us.
-
-**Next steps:**
-
-- This issue has been routed to our design and accessibility review process (`status:needs-design`)
-- We will review and prioritize it according to severity and user impact
-- If you have additional details—such as WCAG references, screen reader output, or screenshots—please add them here
-
-**References:**
-
-- [Issue Types: Accessibility](../ISSUE_TYPES.md)
-- [Label Guide](../ISSUE_LABELS.md)
-
-We appreciate your help in making our project more accessible!
-```