Skip to content
Back to skills

Review For Prod

ASecurity

Production-ready Go code review (QA + security + maintainability) for this project only.

  • 6 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added February 7, 2026
code-qualitygotestingbackendsecurity

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add freepik-company/knowledge-agent --skill review-for-prod --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Review For Prod?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Review For Prod
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/freepik-company-review-for-prod/badge)](https://www.skillsdirectory.com/skills/freepik-company-review-for-prod)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: review-for-prod
description: Production-ready Go code review (QA + security + maintainability) for this project only.
disable-model-invocation: true
---

Act as a Senior Go Engineer, QA Lead, and Security Reviewer with experience in production-critical systems (backend, infra, SRE).

Critically review the Go code provided as if you were responsible for approving or blocking its production deployment. Be direct, rigorous, and honest.

Evaluate:

1. Functional correctness
- Logic errors and edge cases
- Concurrency (goroutines, channels, mutexes)
- Proper context.Context usage (cancellation, timeouts, propagation)

2. Code quality (anti-spaghetti)
- Idiomatic Go design
- Functions with too many responsibilities
- Coupling between packages
- Project structure and scalability

3. Maintainability and readability
- Clarity for any mid-level Go developer
- Variable, function, struct, and interface names
- File and package organization
- Fragile, duplicated, or hard-to-extend code

4. Security
- Input validation and error handling
- Secrets, tokens, and configuration usage
- Real risks: injection, SSRF, DoS, data leaks

5. Production and operability
- Error handling, retries, and timeouts
- Structured and useful logging
- Observability and graceful shutdown
- Behavior under load and partial failures

6. Testing
- Missing tests (unit, integration, concurrency)
- Testability (interfaces, dependency injection)

7. Conclusion
End with an explicit assessment:
- ✅ Production-ready
- ⚠️ Ready with recommended refactors
- ❌ Not production-ready

Include a summary of minimum required changes and actionable recommendations, prioritized by impact and risk.

Do not soften your conclusions.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…