go

Coordinate development lifecycle phases from verification to shipping.

3|1|Updated Mar 23, 2026

Search Tags:#automation #go #verify #ship #development-lifecycle #code-review #ci

Ready to run

npx skills add https://github.com/malinskibeniamin/skills --skill go-malinskibeniamin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: go
Source: https://github.com/malinskibeniamin/skills/tree/main/go
Command: npx skills add https://github.com/malinskibeniamin/skills --skill go-malinskibeniamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Go skill orchestrates the end-to-end development lifecycle phases from verification to shipping, reducing manual handoffs and ensuring consistent quality gates.

Core Features & Use Cases

Phase 4: Verify all changes with type checks, lint, tests, and optional browser tests.
Phase 4b: Self-review and adversarial-review loops to triage findings before shipping.
Phase 5 & 5b: Simplify, deslop, commit-push-pr, and monitor CI until approvals are received.
Phase 6: Compound when patterns emerge or migrations require durable rules and guards.
Entry Gate: Ensure a clean working tree before starting and auto-spawn worktrees as needed.

Quick Start

Run the go workflow to automatically progress through verify, self-review, simplify, deslop, and commit-push-pr.

Frequently Asked Questions about go

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

FAQPage Schema

How do I automate the development lifecycle from code verification to shipping?▼

Automate the development lifecycle by orchestrating end-to-end phases from verification to shipping. The workflow coordinates type checks, linting, tests, self-review loops, and PR handoffs across CI to reduce manual handoffs and enforce consistent quality gates.

What is the best way to orchestrate CI checks and code review loops together?▼

Orchestrating CI checks and code review loops involves implementing automated gates for type checking, linting, and tests, followed by self-review and adversarial-review phases. This ensures findings are triaged and code is simplified before commit-push-pr and CI monitoring begin.

How do I set up automated quality gates for linting, type checking, and tests?▼

Automated quality gates for linting, type checking, and tests are configured during the verification phase. The workflow requires a clean working tree before starting, automatically spawning worktrees as needed to isolate changes and run checks.

Can I include browser tests and dependency upgrades in my automated PR workflow?▼

Browser tests and dependency upgrades are supported within the automated PR workflow. The lifecycle orchestration implements specific gates for optional browser tests, dependency upgrades, visual reviews, and fresh-eyes PR handoffs to ensure comprehensive validation before shipping.

Do I need a clean working tree before starting automated code verification?▼

A clean working tree is required before starting automated code verification. The entry gate enforces this prerequisite and automatically spawns worktrees as needed to isolate work, ensuring the verification and shipping phases execute without state conflicts.

When should I use automated self-review loops before creating a pull request?▼

Automated self-review loops should be used after implementation is complete and before creating a pull request. They triage findings from verification checks, allowing you to simplify and deslop code before committing and pushing for final CI monitoring and approvals.