docs: add contributing, security, support, and code-of-conduct docs; add docs index

CHANGES
- Add CODE_OF_CONDUCT defining respectful, collaborative community behavior
- Add CONTRIBUTING with setup, testing, PR, changelog requirements
- Add SECURITY policy with reporting process and response timelines
- Add SUPPORT guide for bugs, features, discussions, expectations
- Add docs README indexing guides, quick starts, contributor essentials

.vscode/settings.json

@@ -56,6 +56,7 @@
 		"godotenv",
 		"gofmt",
 		"goimports",
+		"golint",
 		"gomod",
 		"gonic",
 		"goopenai",

cmd/generate_changelog/incoming/1729.txt

@@ -0,0 +1,7 @@
+### PR [#1729](https://github.com/danielmiessler/Fabric/pull/1729) by [ksylvan](https://github.com/ksylvan): Add GitHub Community Health Documents
+
+- Add CODE_OF_CONDUCT defining respectful, collaborative community behavior
+- Add CONTRIBUTING with setup, testing, PR, changelog requirements
+- Add SECURITY policy with reporting process and response timelines
+- Add SUPPORT guide for bugs, features, discussions, expectations
+- Add docs README indexing guides, quick starts, contributor essentials

docs/CODE_OF_CONDUCT.md

@@ -0,0 +1,26 @@
+# Code of Conduct
+
+## Our Expectation
+
+We expect all contributors and community members to act with basic human decency and common sense.
+
+This project exists to help people augment their capabilities with AI, and we welcome contributions from anyone who shares this mission. We assume good faith and trust that everyone involved is here to build something valuable together.
+
+## Guidelines
+
+- **Be respectful**: Treat others as you'd want to be treated in a professional setting
+- **Be constructive**: Focus on the work and help make the project better
+- **Be collaborative**: We're all working toward the same goal - making Fabric more useful
+- **Use good judgment**: If you're not sure whether something is appropriate, it probably isn't
+
+## Reporting Issues
+
+If someone is being genuinely disruptive or harmful, please email the maintainers directly. We'll address legitimate concerns promptly and fairly.
+
+## Enforcement
+
+Maintainers reserve the right to remove content and restrict access for anyone who consistently acts in bad faith or disrupts the community.
+
+---
+
+*This project assumes contributors are adults who can work together professionally. If you can't do that, this isn't the right place for you.*

docs/CONTRIBUTING.md

@@ -0,0 +1,155 @@
+# Contributing to Fabric
+
+Thanks for contributing to Fabric! Here's what you need to know to get started quickly.
+
+## Quick Setup
+
+### Prerequisites
+
+- Go 1.24+ installed
+- Git configured with your details
+
+### Getting Started
+
+```bash
+# Clone and setup
+git clone https://github.com/danielmiessler/fabric.git
+cd fabric
+go build -o fabric ./cmd/fabric
+./fabric --setup
+
+# Run tests
+go test ./...
+```
+
+## Development Guidelines
+
+### Code Style
+
+- Follow standard Go conventions (`gofmt`, `golint`)
+- Use meaningful variable and function names
+- Write tests for new functionality
+- Keep functions focused and small
+
+### Commit Messages
+
+Use descriptive commit messages:
+
+```text
+feat: add new pattern for code analysis
+fix: resolve OAuth token refresh issue
+docs: update installation instructions
+```
+
+### Project Structure
+
+- `cmd/` - Executable commands
+- `internal/` - Private application code
+- `data/patterns/` - AI patterns
+- `docs/` - Documentation
+
+## Pull Request Process
+
+### Changelog Generation (REQUIRED)
+
+Before submitting your PR, generate a changelog entry:
+
+```bash
+cd cmd/generate_changelog
+go build -o generate_changelog .
+./generate_changelog --incoming-pr YOUR_PR_NUMBER
+```
+
+**Requirements:**
+
+- PR must be open and mergeable
+- Working directory must be clean
+- GitHub token available (GITHUB_TOKEN env var)
+
+**Optional flags:**
+
+- `--ai-summarize` - Enhanced AI-generated summaries
+- `--push` - Auto-push the changelog commit
+
+### PR Guidelines
+
+1. Fork the repository
+2. Create a feature branch
+3. Make your changes
+4. Write/update tests
+5. Generate changelog entry (see above)
+6. Submit PR with clear description
+
+### Review Process
+
+- PRs require maintainer review
+- Address feedback promptly
+- Keep PRs focused on single features/fixes
+- Update changelog if you make significant changes
+
+## Testing
+
+### Run Tests
+
+```bash
+# All tests
+go test ./...
+
+# Specific package
+go test ./internal/cli
+
+# With coverage
+go test -cover ./...
+```
+
+### Test Requirements
+
+- Unit tests for core functionality
+- Integration tests for external dependencies
+- Examples in documentation
+
+## Patterns
+
+### Creating Patterns
+
+Patterns go in `data/patterns/[pattern-name]/system.md`:
+
+```markdown
+# IDENTITY and PURPOSE
+You are an expert at...
+
+# STEPS
+- Step 1
+- Step 2
+
+# OUTPUT
+- Output format requirements
+
+# EXAMPLE
+Example output here
+```
+
+### Pattern Guidelines
+
+- Use clear, actionable language
+- Provide specific output formats
+- Include examples when helpful
+- Test with multiple AI providers
+
+## Documentation
+
+- Update README.md for new features
+- Add docs to `docs/` for complex features
+- Include usage examples
+- Keep documentation current
+
+## Getting Help
+
+- Check existing issues first
+- Ask questions in discussions
+- Tag maintainers for urgent issues
+- Be patient - maintainers are volunteers
+
+## License
+
+By contributing, you agree your contributions will be licensed under the MIT License.

docs/README.md

@@ -0,0 +1,88 @@
+# Fabric Documentation
+
+Welcome to the Fabric documentation! This directory contains detailed guides and technical documentation for various features and components of Fabric.
+
+## 📚 Available Documentation
+
+### Core Features
+
+**[Automated-Changelog-Usage.md](./Automated-Changelog-Usage.md)**
+Complete guide for developers on using the automated changelog system. Covers the workflow for generating PR changelog entries during development, including setup, validation, and CI/CD integration.
+
+**[YouTube-Processing.md](./YouTube-Processing.md)**
+Comprehensive guide for processing YouTube videos and playlists with Fabric. Covers transcript extraction, comment processing, metadata retrieval, and advanced yt-dlp configurations.
+
+**[Using-Speech-To-Text.md](./Using-Speech-To-Text.md)**
+Documentation for Fabric's speech-to-text capabilities using OpenAI's Whisper models. Learn how to transcribe audio and video files and process them through Fabric patterns.
+
+### User Interface & Experience
+
+**[Desktop-Notifications.md](./Desktop-Notifications.md)**
+Guide to setting up desktop notifications for Fabric commands. Useful for long-running tasks and multitasking scenarios with cross-platform notification support.
+
+**[Shell-Completions.md](./Shell-Completions.md)**
+Instructions for setting up intelligent tab completion for Fabric in Zsh, Bash, and Fish shells. Includes automated installation and manual setup options.
+
+**[Gemini-TTS.md](./Gemini-TTS.md)**
+Complete guide for using Google Gemini's text-to-speech features with Fabric. Covers voice selection, audio generation, and integration with Fabric patterns.
+
+### Development & Architecture
+
+**[Automated-ChangeLog.md](./Automated-ChangeLog.md)**
+Technical documentation outlining the automated CHANGELOG system architecture for CI/CD integration. Details the infrastructure and workflow for maintainers.
+
+**[Project-Restructured.md](./Project-Restructured.md)**
+Project restructuring plan and architectural decisions. Documents the transition to standard Go conventions and project organization improvements.
+
+**[NOTES.md](./NOTES.md)**
+Development notes on refactoring efforts, model management improvements, and architectural changes. Includes technical details on vendor and model abstraction.
+
+### Audio Resources
+
+**[voices/README.md](./voices/README.md)**
+Index of Gemini TTS voice samples demonstrating different AI voice characteristics available in Fabric.
+
+## 🗂️ Additional Resources
+
+### Configuration Files
+
+- `./notification-config.yaml` - Example notification configuration
+
+### Images
+
+- `images/` - Screenshots and visual documentation assets
+  - `fabric-logo-gif.gif` - Animated Fabric logo
+  - `fabric-summarize.png` - Screenshot of summarization feature
+  - `svelte-preview.png` - Web interface preview
+
+## 🚀 Quick Start
+
+New to Fabric? Start with these essential docs:
+
+1. **[../README.md](../README.md)** - Main project README with installation and basic usage
+2. **[Shell-Completions.md](./Shell-Completions.md)** - Set up tab completion for better CLI experience
+3. **[YouTube-Processing.md](./YouTube-Processing.md)** - Learn one of Fabric's most popular features
+4. **[Desktop-Notifications.md](./Desktop-Notifications.md)** - Get notified when long tasks complete
+
+## 🔧 For Contributors
+
+Contributing to Fabric? These docs are essential:
+
+1. **[./CONTRIBUTING.md](./CONTRIBUTING.md)** - Contribution guidelines and setup
+2. **[Automated-Changelog-Usage.md](./Automated-Changelog-Usage.md)** - Required workflow for PR submissions
+3. **[Project-Restructured.md](./Project-Restructured.md)** - Understanding project architecture
+4. **[NOTES.md](./NOTES.md)** - Current development priorities and patterns
+
+## 📝 Documentation Standards
+
+When adding new documentation:
+
+- Use clear, descriptive filenames
+- Include practical examples and use cases
+- Update this README index with your new docs
+- Follow the established markdown formatting conventions
+- Test all code examples before publication
+
+---
+
+*For general help and support, see [./SUPPORT.md](./SUPPORT.md)*

docs/SECURITY.md

@@ -0,0 +1,158 @@
+# Security Policy
+
+## Supported Versions
+
+We aim to provide security updates for the latest version of Fabric.
+
+We recommend always using the latest version of Fabric for security fixes and improvements.
+
+## Reporting Security Vulnerabilities
+
+**Please DO NOT report security vulnerabilities through public GitHub issues.**
+
+### Preferred Reporting Method
+
+Send security reports directly to: **<kayvan@sylvan.com>** and CC to the project maintainer at **<daniel@danielmiessler.com>**
+
+### What to Include
+
+Please provide the following information:
+
+1. **Vulnerability Type**: What kind of security issue (e.g., injection, authentication bypass, etc.)
+2. **Affected Components**: Which parts of Fabric are affected
+3. **Impact Assessment**: What could an attacker accomplish
+4. **Reproduction Steps**: Clear steps to reproduce the vulnerability
+5. **Proposed Fix**: If you have suggestions for remediation
+6. **Disclosure Timeline**: Your preferred timeline for public disclosure
+
+### Example Report Format
+
+```text
+Subject: [SECURITY] Brief description of vulnerability
+
+Vulnerability Type: SQL Injection
+Affected Component: Pattern database queries
+Impact: Potential data exposure
+Severity: High
+
+Reproduction Steps:
+1. Navigate to...
+2. Submit payload: ...
+3. Observe...
+
+Evidence:
+[Screenshots, logs, or proof of concept]
+
+Suggested Fix:
+Use parameterized queries instead of string concatenation...
+```
+
+## Security Considerations
+
+### API Keys and Secrets
+
+- Never commit API keys to the repository
+- Store secrets in environment variables or secure configuration
+- Use the built-in setup process for key management
+- Regularly rotate API keys
+
+### Input Validation
+
+- All user inputs are validated before processing
+- Special attention to pattern definitions and user content
+- URL validation for web scraping features
+
+### AI Provider Integration
+
+- Secure communication with AI providers (HTTPS/TLS)
+- Token handling follows provider best practices
+- No sensitive data logged or cached unencrypted
+
+### Network Security
+
+- Web server endpoints properly authenticated when required
+- CORS policies appropriately configured
+- Rate limiting implemented where necessary
+
+## Vulnerability Response Process
+
+1. **Report Received**: We'll acknowledge receipt within 24 hours
+2. **Initial Assessment**: We'll evaluate severity and impact within 72 hours
+3. **Investigation**: We'll investigate and develop fixes
+4. **Fix Development**: We'll create and test patches
+5. **Coordinated Disclosure**: We'll work with reporter on disclosure timeline
+6. **Release**: We'll release patched version with security advisory
+
+### Timeline Expectations
+
+- **Critical**: 1-7 days
+- **High**: 7-30 days
+- **Medium**: 30-90 days
+- **Low**: Next scheduled release
+
+## Bug Bounty
+
+We don't currently offer a formal bug bounty program, but we deeply appreciate security research and will:
+
+- Acknowledge contributors in release notes
+- Provide credit in security advisories
+- Consider swag or small rewards for significant findings
+
+## Security Best Practices for Users
+
+### Installation
+
+- Download Fabric only from official sources
+- Verify checksums when available
+- Keep installations up to date
+
+### Configuration
+
+- Use strong, unique API keys
+- Don't share configuration files containing secrets
+- Set appropriate file permissions on config directories
+
+### Usage
+
+- Be cautious with patterns that process sensitive data
+- Review AI provider terms for data handling
+- Consider using local models for sensitive content
+
+## Known Security Limitations
+
+### AI Provider Dependencies
+
+Fabric relies on external AI providers. Security depends partly on:
+
+- Provider security practices
+- Data transmission security
+- Provider data handling policies
+
+### Pattern Execution
+
+Custom patterns could potentially:
+
+- Process sensitive inputs inappropriately
+- Generate outputs containing sensitive information
+- Be used for adversarial prompt injection
+
+**Recommendation**: Review patterns carefully, especially those from untrusted sources.
+
+## Security Updates
+
+Security updates are distributed through:
+
+- GitHub Releases with security tags
+- Security advisories on GitHub
+- Project documentation updates
+
+Subscribe to the repository to receive notifications about security updates.
+
+## Contact
+
+For non-security issues, please use GitHub issues.
+For security concerns, email: **<kayvan@sylvan.com>** and CC to **<daniel@danielmiessler.com>**
+
+---
+
+*We take security seriously and appreciate the security research community's help in keeping Fabric secure.*

docs/SUPPORT.md

@@ -0,0 +1,148 @@
+# Support
+
+## Getting Help with Fabric
+
+Need help with Fabric? Here are the best ways to get assistance:
+
+## 📖 Documentation First
+
+Before reaching out, check these resources:
+
+- **[README.md](../README.md)** - Installation, usage, and examples
+- **[docs/](./README.md)** - Detailed documentation
+- **[Patterns](../data/patterns/)** - Browse available AI patterns
+
+## 🐛 Bug Reports
+
+Found a bug? Please create an issue:
+
+**[Report a Bug](https://github.com/danielmiessler/fabric/issues/new?template=bug.yml)**
+
+Include:
+
+- Fabric version (`fabric --version`)
+- Operating system
+- Steps to reproduce
+- Expected vs actual behavior
+- Error messages/logs
+
+## 💡 Feature Requests
+
+Have an idea for Fabric? We'd love to hear it:
+
+**[Request a Feature](https://github.com/danielmiessler/fabric/issues/new)**
+
+Describe:
+
+- What you want to achieve
+- Why it would be useful
+- How you envision it working
+- Any alternatives you've considered
+
+## 🤔 Questions & Discussions
+
+For general questions, usage help, or community discussion:
+
+**[GitHub Discussions](https://github.com/danielmiessler/fabric/discussions)**
+
+Great for:
+
+- "How do I...?" questions
+- Sharing patterns you've created
+- Getting community advice
+- Feature brainstorming
+
+## 🏷️ Issue Labels
+
+When creating issues, maintainers will add appropriate labels:
+
+- `bug` - Something isn't working
+- `enhancement` - New feature request
+- `documentation` - Documentation improvements
+- `help wanted` - Community contributions welcome
+- `good first issue` - Great for new contributors
+- `question` - General questions
+- `pattern` - Related to AI patterns
+
+## 📋 Issue Templates
+
+We provide templates to help you create detailed reports:
+
+- **Bug Report** - Structured bug reporting
+- **Feature Request** - Detailed feature proposals
+- **Pattern Submission** - New pattern contributions
+
+## 🔒 Security Issues
+
+**DO NOT create public issues for security vulnerabilities.**
+
+See our [Security Policy](./SECURITY.md) for proper reporting procedures.
+
+## ⚡ Response Times
+
+We're a community-driven project with volunteer maintainers:
+
+- **Bugs**: We aim to acknowledge within 48 hours
+- **Features**: Response time varies based on complexity
+- **Questions**: Community often responds quickly
+- **Security**: See security policy for timelines
+
+## 🛠️ Self-Help Tips
+
+Before creating an issue, try:
+
+1. **Update Fabric**: `go install github.com/danielmiessler/fabric/cmd/fabric@latest`
+2. **Check existing issues**: Someone might have the same problem
+3. **Run setup**: `fabric --setup` can fix configuration issues
+4. **Test minimal example**: Isolate the problem
+
+## 🤝 Community Guidelines
+
+When asking for help:
+
+- Be specific and provide context
+- Include relevant details and error messages
+- Be patient - maintainers are volunteers
+- Help others when you can
+- Say thanks when someone helps you
+
+## 📞 Emergency Contact
+
+For urgent security issues only:
+
+- Email: <security@fabric.ai> (if available)
+- Maintainer: <daniel@danielmiessler.com>
+
+## 🎯 What We Can Help With
+
+✅ **We can help with:**
+
+- Installation and setup issues
+- Usage questions and examples
+- Bug reports and fixes
+- Feature discussions
+- Pattern creation guidance
+- Integration questions
+
+❌ **We cannot help with:**
+
+- Custom development for your specific use case
+- Troubleshooting your specific AI provider issues
+- General AI or programming tutorials
+- Commercial support agreements
+
+## 💪 Contributing Back
+
+The best way to get help is to help others:
+
+- Answer questions in discussions
+- Improve documentation
+- Share useful patterns
+- Report bugs clearly
+- Review pull requests
+
+See our [Contributing Guide](./CONTRIBUTING.md) for details.
+
+---
+
+*Remember: We're all here to make Fabric better. Be kind, be helpful, and let's build something amazing together!*