go-engineering

Load the canonical Go engineering skill surface for project governance.

3|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ldilov/harness-forge --skill go-engineering-ldilov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-engineering
Source: https://github.com/ldilov/harness-forge/tree/main/.agents/skills/go-engineering
Command: npx skills add https://github.com/ldilov/harness-forge --skill go-engineering-ldilov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a discovery wrapper that routes to the canonical Go engineering skill surface, ensuring the active context uses the canonical surface without duplicating guidance.

Core Features & Use Cases

  • Discovery wrapper that loads the canonical Go engineering skill surface.
  • Allows pulling deeper rules, knowledge, workflows, and provenance context on demand.
  • Use Case: Initialize a Go project with the canonical surface for consistent engineering behavior.

Quick Start

Activate the Go engineering discovery wrapper to load the canonical Go engineering surface for immediate use.

Frequently Asked Questions about go-engineering

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

FAQPage Schema
How do I load the canonical Go engineering surface for my project?

To load the canonical Go engineering surface, activate the discovery wrapper to initialize your Go project with consistent engineering behavior, enabling access to deeper rules, knowledge, workflows, and provenance context on demand.

What is a Go engineering discovery wrapper used for?

A Go engineering discovery wrapper routes your active context to the canonical Go engineering skill surface, ensuring consistent engineering behavior without duplicating guidance across your Go project workflows.

When do I need to initialize a Go project with a canonical surface?

You need to initialize a Go project with the canonical surface when your project requires loading the canonical Go execution surface first to perform engineering tasks and govern rules, knowledge, and provenance.

Can I fetch deeper workflow and provenance context on demand with this surface?

Yes, after loading the canonical Go engineering surface, you can fetch deeper rules, knowledge, workflows, and provenance context on demand to support your specific engineering tasks.

Does the canonical Go surface duplicate engineering guidance across workflows?

No, the canonical Go surface avoids duplicating guidance by using a discovery wrapper that routes directly to the canonical execution surface, ensuring your active context remains consistent.

What is the best way to govern engineering rules and provenance in Go projects?

The best way to govern engineering rules and provenance in Go projects is to load the canonical execution surface first, then fetch the required deeper rules, knowledge, workflows, and provenance context on demand.