go-engineer

Guide maintenance and documentation for archived Go engine and API server code.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Develonaut/bnto --skill go-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-engineer
Source: https://github.com/Develonaut/bnto/tree/main/.claude/skills/go-engineer
Command: npx skills add https://github.com/Develonaut/bnto --skill go-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Go engineer persona provides authoritative guidance for maintaining and referencing the archived Go engine and API server, capturing legacy patterns and best practices for future work.

Core Features & Use Cases

  • Guided maintenance of archive/engine-go and archive/api-go codebases with clear, actionable recommendations.
  • Documentation and patterns for Go project structure, error handling, and testing in legacy contexts.
  • Reference-ready insights to accelerate onboarding of new engineers working with archived code.

Quick Start

Ask the Go engineer to review the archived Go engine and API server in archive/engine-go/ and archive/api-go/ and propose a maintenance plan.

Frequently Asked Questions about go-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain legacy Go engine and API server codebases?

To maintain legacy Go engine and API server codebases, apply persona-based guidance for archive/engine-go/ and archive/api-go/ directories, enforcing coding standards and generating actionable maintenance recommendations.

What Go patterns work best for archived legacy code?

Go patterns for archived legacy code focus on project structure, error handling, and testing within legacy contexts, providing reference-ready insights to accelerate onboarding for new engineers.

How do I review an archived Go API server for future reference?

Reviewing an archived Go API server involves analyzing the archive/api-go/ codebase to provide documentation, enforce coding standards, and propose a clear maintenance plan for future reference.

Can I get help with Go testing and documentation for archived engine code?

Yes, you can get help with Go testing and documentation for archived engine code in archive/engine-go/, receiving guidance on testing strategies and documentation patterns for legacy contexts.

What is the best way to onboard new engineers to an archived Go project?

The best way to onboard new engineers to an archived Go project is using reference-ready insights that capture legacy patterns, best practices, and actionable maintenance recommendations for the codebase.

Why should I enforce coding standards when referencing archived Go code?

Enforcing coding standards when referencing archived Go code ensures maintainability and captures legacy patterns, providing authoritative guidance for future work on the engine and API server.