Add comprehensive error checking and feedback loops documentation

This commit is contained in:
2025-04-22 22:01:38 +01:00
parent e5b0181baf
commit 953bf3f6bb
2 changed files with 556 additions and 2 deletions

View File

@@ -87,7 +87,12 @@ Always run PHPCS and PHPCBF locally before committing code to ensure it meets th
## Common Tasks
For detailed instructions on common tasks like creating releases, adding features, fixing bugs, and testing previous versions, see **@.ai-workflows/release-process.md**.
For detailed instructions on common tasks, refer to these workflow documents:
* **@.ai-workflows/release-process.md**: Creating releases, versioning, and deployment
* **@.ai-workflows/feature-development.md**: Adding new features and functionality
* **@.ai-workflows/bug-fixing.md**: Diagnosing and fixing issues
* **@.ai-workflows/error-checking-feedback-loops.md**: Monitoring CI/CD pipelines and establishing feedback loops
## Avoiding Cross-Repository Confusion
@@ -153,6 +158,28 @@ When working with this repository, remember these preferences:
1. Follow WordPress coding standards
2. Use OOP approach with namespaced classes
3. Keep code modular and maintainable
3. Reference these preferences in future interactions
4. Reference these preferences in future interactions
This ensures consistency across coding sessions and reduces the need for developers to repeatedly explain their preferences.
## Autonomous CI/CD and Error Handling
This repository is set up for autonomous continuous integration and deployment with minimal human intervention. As an AI assistant, you should:
1. **Monitor CI/CD Pipelines**: Use the GitHub API to check workflow status and identify failures
2. **Diagnose Issues**: Analyze error logs and determine root causes
3. **Implement Fixes**: Make necessary code changes to resolve issues
4. **Verify Solutions**: Ensure fixes pass all tests and quality checks
5. **Document Resolutions**: Update documentation with solutions for future reference
For detailed instructions on establishing feedback loops and error checking processes, see **@.ai-workflows/error-checking-feedback-loops.md**.
### When to Consult Humans
Only consult humans for:
* Product design decisions
* Security-critical changes
* Major architectural decisions
* Access to information not available through APIs or terminal
* Novel problems without precedent or documented solutions