go-api-record

record a Go API service that logs and timestamps every incoming request and outgoing response, enabling precise latency and reliability tracking for your microservice architecture.

3|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/standard-librarian/context-engineer --skill go-api-record
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-api-record
Source: https://github.com/standard-librarian/context-engineer/tree/main/examples/go-echo-app/skills/user/go-api-record
Command: npx skills add https://github.com/standard-librarian/context-engineer --skill go-api-record

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers and teams systematically record critical architectural decisions and production failures related to Go API development, fostering knowledge sharing and preventing recurring issues.

Core Features & Use Cases

  • Record Architectural Decisions (ADRs): Document choices about frameworks, libraries, patterns, and design principles.
  • Record Failures: Log incidents, their root causes, symptoms, resolutions, and prevention strategies.
  • Use Case: After deciding to use GORM for database interactions in your Go application, you can use this skill to create an ADR detailing the decision, context, and alternatives considered. If a production incident occurs due to a database connection leak, you can use the skill to record the failure, its impact, and the steps taken to resolve and prevent it.

Quick Start

Use the go-api-record skill to record a new architectural decision about using Echo for your Go REST API.

Frequently Asked Questions about go-api-record

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

FAQPage Schema
How do I document architectural decisions for a Go API?

To document architectural decisions for a Go API, record technology choices, design patterns, and alternatives considered. This approach captures detailed context surrounding framework selections to foster team knowledge sharing and prevent recurring design issues.

What is the best way to record Go API production failures and incidents?

Recording Go API production failures involves logging detailed incident context, root causes, symptoms, and resolutions. This systematic failure documentation captures prevention strategies to help development teams avoid repeating similar production issues.

How do I store and retrieve Go API ADRs after creating them?

Go API ADRs are stored and retrieved by integrating with a context engineering API for persistent storage. This ensures architectural decisions and failure incidents remain accessible for future reference and team knowledge sharing.

Can I use this to log a database connection leak in my Go application?

Yes, you can log a database connection leak in your Go application by recording the production incident. The skill documents the failure impact, root cause, and the specific resolution and prevention steps taken.

When do I need to create an ADR for my Go REST API development?

You need to create an ADR for Go REST API development when making significant technology choices, such as selecting frameworks or libraries. Documenting these design principles and patterns captures the context and alternatives evaluated during the decision process.