gh:compound

Coordinate subagents to document solved problems into YAML-frontmatter solution docs.

2|1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill gh-compound
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh:compound
Source: https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI/tree/main/plugins/galeharness-cli/skills/gh-compound
Command: npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill gh-compound

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gale-task, gale-memory, gh.

What problem does it solve?

Documents recently solved problems by coordinating multiple subagents to create structured, searchable knowledge assets that can be reused to accelerate future work.

Core Features & Use Cases

  • Orchestrates parallel subagents (Context Analyzer, Solution Extractor, Related Docs Finder, Session Historian) to produce a fully documented solution with YAML frontmatter.
  • Writes final docs under docs/solutions in category-based directories, with category and problem_type metadata for discovery and reuse.
  • Integrates optional context from memory and prior sessions to enrich the documentation and reduce duplication.

Quick Start

Run gh:compound to document the most recent fix and its context.

Frequently Asked Questions about gh:compound

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

FAQPage Schema
How do I document solved problems to build a searchable team knowledge base?

To document solved problems and build a team knowledge base, this Skill coordinates multiple subagents to extract solutions and context, generating structured YAML-frontmatter documents in docs/solutions for future discovery and reuse.

How does multi-agent workflow extract solutions and generate structured documentation?

The multi-agent workflow extracts solutions by orchestrating parallel subagents for context analysis, solution extraction, related docs finding, and session history review, assembling validated YAML-frontmatter documents categorized by problem type.

Can I use memory and prior sessions to enrich problem solving documentation?

Yes, you can enrich problem solving documentation by integrating optional context from memory and prior sessions, which reduces duplication and adds valuable historical context to the newly created knowledge artifacts.

What is the best way to categorize bug fixes and knowledge tracks in solution docs?

The best way to categorize bug fixes and knowledge tracks is by validating YAML frontmatter against a schema and assigning the problem_type metadata, sorting documents into category-based directories under docs/solutions.

Do I need specific dependencies to run the gh:compound knowledge management workflow?

To run the gh:compound knowledge management workflow, you need the gale-task, gale-memory, and gh dependencies installed to support subagent coordination, context integration, and document assembly.

Why should I use a multi-agent approach over manual documentation for team solutions?

A multi-agent approach surpasses manual documentation by automating context analysis and solution extraction in parallel, ensuring structured schema validation and comprehensive knowledge artifacts without manual formatting overhead.