ggcoder

GGCoder

GGCoder is an extended version of Superpowers - a complete software development workflow for coding agents. It includes all the original Superpowers capabilities plus specialized code review and fixing for GridGain 9 / Apache Ignite 3 codebases.

What's New in GGCoder

In addition to the core Superpowers workflow (brainstorming, planning, TDD, subagent-driven development), GGCoder adds:

• 5 Specialized Reviewers - Domain-specific code review for GridGain/Ignite
• 6 Automated Fixers - Apply fixes using patterns from 100+ real PRs
• 9 Pattern Skills - Concurrency, resource cleanup, async, testing patterns
• Layered Review - GridGain reviewers run first, then architecture review

GridGain Reviewers

Reviewer	Focus
gg-safety-reviewer	Concurrency, resource leaks, null safety, type safety
gg-quality-reviewer	Dead code, duplication, logging, style
gg-testing-reviewer	Coverage gaps, assertions, flakiness
gg-cpp-reviewer	C++ headers, ownership, shell scripts
gg-build-reviewer	Dependencies, API consistency

How Layered Review Works

When you use ggcoder:subagent-driven-development or ggcoder:requesting-code-review:

Pass 1: GridGain Domain Reviewers (Parallel)
├── .java/.cs files → gg-safety + gg-quality + gg-testing
├── .cpp/.h files   → gg-cpp
└── build.gradle    → gg-build

Pass 2: Architecture Review
└── code-reviewer (plan alignment, design patterns)

How it works

It starts from the moment you fire up your coding agent. As soon as it sees that you're building something, it doesn't just jump into trying to write code. Instead, it steps back and asks you what you're really trying to do.

Once it's teased a spec out of the conversation, it shows it to you in chunks short enough to actually read and digest.

After you've signed off on the design, your agent puts together an implementation plan that's clear enough for an enthusiastic junior engineer with poor taste, no judgement, no project context, and an aversion to testing to follow. It emphasizes true red/green TDD, YAGNI (You Aren't Gonna Need It), and DRY.

Next up, once you say "go", it launches a subagent-driven-development process, having agents work through each engineering task, inspecting and reviewing their work, and continuing forward. It's not uncommon for Claude to be able to work autonomously for a couple hours at a time without deviating from the plan you put together.

There's a bunch more to it, but that's the core of the system. And because the skills trigger automatically, you don't need to do anything special.

Credits

GGCoder is built on top of Superpowers by Jesse Vincent. If you find this useful, consider sponsoring his opensource work.

Installation

Note: Installation differs by platform. Claude Code or Cursor have built-in plugin marketplaces. Codex and OpenCode require manual setup.

Claude Code (via Plugin Marketplace)

In Claude Code, register the marketplace first:

/plugin marketplace add tapnetix/ggcoder

Then install the plugin:

/plugin install ggcoder@ggcoder-marketplace

Cursor (via Plugin Marketplace)

In Cursor Agent chat, install from marketplace:

/add-plugin ggcoder

or search for "ggcoder" in the plugin marketplace.

Codex

Tell Codex:

Fetch and follow instructions from https://raw.githubusercontent.com/tapnetix/ggcoder/refs/heads/main/.codex/INSTALL.md

Detailed docs: docs/README.codex.md

OpenCode

Tell OpenCode:

Fetch and follow instructions from https://raw.githubusercontent.com/tapnetix/ggcoder/refs/heads/main/.opencode/INSTALL.md

Detailed docs: docs/README.opencode.md

Gemini CLI

gemini extensions install https://github.com/obra/superpowers

To update:

gemini extensions update superpowers

Verify Installation

Start a new session in your chosen platform and ask for something that should trigger a skill (for example, "help me plan this feature" or "let's debug this issue"). The agent should automatically invoke the relevant ggcoder skill.

The Basic Workflow

1. brainstorming - Activates before writing code. Refines rough ideas through questions, explores alternatives, presents design in sections for validation. Saves design document.

2. using-git-worktrees - Activates after design approval. Creates isolated workspace on new branch, runs project setup, verifies clean test baseline.

3. writing-plans - Activates with approved design. Breaks work into bite-sized tasks (2-5 minutes each). Every task has exact file paths, complete code, verification steps.