service

Migrate network-facing servers into Forge service-shaped projects with scaffolding.

4|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/reliant-labs/forge --skill service-reliant-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: service
Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/migration/service
Command: npx skills add https://github.com/reliant-labs/forge --skill service-reliant-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines migrating an existing network-facing codebase into Forge’s service-shaped project structure so you can scaffold, add components, install packs, and reach a green build faster.

Core Features & Use Cases

  • Service scaffolding for network-facing systems: Convert HTTP/gRPC servers, webhook receivers, background workers, operators, and multi-binary cmd/ layouts into a Forge-managed structure.
  • Incremental component migration: Add services, operators, workers (including cron workers), and webhooks one at a time to isolate verification and reduce migration risk.
  • Safe pack installation and generation workflow: Install packs in the correct order relative to the components they extend, then run generation and validation steps to catch misconfigurations early.

Quick Start

Use the migration workflow by running forge new <name>-next --kind service with the appropriate --mod, --service, and --frontend values, then add remaining components and run forge generate and go build ./... once to establish a passing baseline.

Frequently Asked Questions about service

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

FAQPage Schema
How do I migrate an existing HTTP or gRPC server to a microservices architecture?

Migrating a server-shaped project converts existing HTTP or gRPC servers into a consistent Forge-managed architecture by scaffolding services, operators, workers, and webhooks deterministically. It applies to network-facing systems and multi-binary cmd/ layouts.

What is the best way to incrementally add webhooks and cron workers during a codebase migration?

Incremental component migration allows you to add services, operators, cron workers, and webhooks one at a time. This isolates verification at each step, reducing migration risk before running final generation and validation checks.

Can I use Forge CLI to scaffold a Kubernetes controller loop and background workers?

Yes, Forge CLI supports scaffolding for Kubernetes controller loops and background workers. Running forge new with the service kind converts these network-facing systems into a managed structure with deterministic scaffolding.

How do I install packs and run code generation when migrating to Forge?

Install packs in the correct order relative to the components they extend, then run forge generate and go build ./... to establish a passing baseline. This enforces pack-install ordering and includes contract and lint baseline checks.

Does migrating a multi-binary project to Forge require contract and lint baseline checks?

Yes, migrating multi-binary cmd/ layouts to Forge includes guardrails like contract and lint baseline checks. These checks catch misconfigurations early during the generation and validation steps to ensure a green build.