Afrexai Go Production

What This Skill Does

Afrexai Go Production is a specialized engineering companion designed to elevate your Go (Golang) projects from initial prototype to production-grade reliability. By implementing the 'Go Production Engineering' methodology, this skill serves as an architectural advisor, code reviewer, and systematic engineer. It forces adherence to the Standard Go Project Layout, encourages robust error handling, enforces dependency injection best practices, and ensures that your services are observable, testable, and maintainable. It acts as an expert pair programmer that focuses on long-term maintainability over quick hacks.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/1kalin/afrexai-go-production Once installed, you can trigger the agent by referencing the specific phases outlined in the methodology, such as initiating a 'Quick Health Check' for an existing codebase.

Use Cases

• Project Scaffolding: Quickly structure a new microservice using the battle-tested standard Go layout.
• Code Audits: Run a 'Quick Health Check' to identify technical debt, missing test coverage, or poor error handling patterns.
• Dependency Management: Refactor monolithic packages into distinct domains using clean interfaces and proper dependency injection.
• Production Readiness: Prepare a repository for deployment by configuring structured logging, context propagation, and CI/CD pipeline integration.
• Architecture Reviews: Use the 7 Architecture Rules to validate if your package design avoids circular dependencies and maintains clear boundaries.

Example Prompts

• "Afrexai, perform a Quick Health Check on this codebase; I'm concerned about our current error handling and test coverage."
• "Design a dependency injection pattern for a new PostgreSQL repository within my internal/service layer following the 1kalin architecture guide."
• "My project is currently failing the 'Architecture Rules'. How can I restructure my cmd/ and internal/ directories to fix circular imports between the handler and service packages?"

Tips & Limitations

• Tips: Always start with the Quick Health Check to establish a baseline before refactoring. Focus on high-impact areas first, such as context propagation and error wrapping, before moving to structural changes.
• Limitations: This skill is an advisor. While it provides architectural guidance, it cannot automatically rewrite your entire repository. Use it iteratively for specific modules or packages to maintain control over the migration process.