feat: add console logs validation with Next.js auto-removal detection

- Add new check-console-logs.js validation script
- Detects console.log, console.warn, console.error, etc. statements
- Smart Next.js integration: skips validation if removeConsole is enabled
- Supports allowed patterns: development conditions, ESLint disables, error logging
- Includes comprehensive test fixtures for both violations and allowed usage
- Integrates with existing test runner and CI/CD pipeline
- Provides helpful suggestions for console.log alternatives

This validation helps maintain clean production code by catching debug statements
that developers often forget to remove before deployment.

Author: thedaviddias

.github/actions/run-validation-tests/action.yml

@@ -74,6 +74,7 @@ runs:
           "test:jsdoc"
           "test:complexity"
           "test:structure"
+          "test:console-logs"
         )
         
         for script in "${SCRIPTS[@]}"; do

.github/actions/validate-scripts/action.yml

@@ -120,6 +120,7 @@ runs:
           "check-jsdoc.js"
           "check-file-complexity.js"
           "check-directory-structure.js"
+          "check-console-logs.js"
         )
         
         MISSING_SCRIPTS=()

.github/workflows/release-pr.yml

@@ -5,6 +5,11 @@ on:
   pull_request:
     types: [opened, synchronize, reopened]
 
+permissions:
+  contents: read
+  pull-requests: write
+  issues: write
+
 jobs:
   check-if-release-pr:
     name: Check if Release PR

CONTRIBUTING.md

@@ -25,23 +25,21 @@ Enhancement suggestions are tracked as GitHub issues. When creating an enhanceme
 
 ### 🔧 Adding New Guardrails
 
-Want to add a new validation script? Great! Here's how:
+Want to add a new validation rule? We have a comprehensive guide that covers the entire process!
 
+📚 **[See the Complete Guide for Adding New Validation Rules](../docs/CONTRIBUTING-NEW-RULES.md)**
+
+This guide covers:
+- Creating shared validators and standalone scripts
+- Setting up test infrastructure
+- ESLint plugin integration
+- GitHub Actions configuration
+- Documentation requirements
+- Example templates and best practices
+
+For a quick overview:
 1. **Create the validation script** in `scripts/validation/`
-2. **Follow the existing pattern**:
-   ```javascript
-   // check-your-rule.js
-   const RULE_NAME = 'your-rule';
-   const DEFAULT_OPTIONS = {
-     // Your default configuration
-   };
-   
-   function validate(files, options = {}) {
-     // Your validation logic
-   }
-   
-   module.exports = { validate, RULE_NAME };
-   ```
+2. **Follow the existing pattern** from other validation scripts
 3. **Add tests** for your guardrail
 4. **Update the documentation** in README.md
 5. **Add examples** in docs/EXAMPLES.md

README.md

@@ -471,7 +471,11 @@ We welcome contributions! Whether it's:
 2. Add test fixtures for new validation rules
 3. Update documentation if needed
 
-See our [Contributing Guide](./CONTRIBUTING.md) for details.
+### 📚 Contributing Resources
+
+- [Contributing Guide](./CONTRIBUTING.md) - General contribution guidelines
+- [Adding New Validation Rules](./docs/CONTRIBUTING-NEW-RULES.md) - Comprehensive step-by-step guide for adding new rules
+- [Examples](./docs/EXAMPLES.md) - Usage examples and patterns
 
 ## 📊 Stats & Community