console-rendering
$
npx mdskill add github/gh-aw/console-renderingRenders styled terminal output using Go struct tags in gh-aw
- Displays structured data with custom headers and formatting in the terminal
- Uses Go struct tags to define rendering rules and styles
- Applies formatting types like numbers, currency, and omits zero values
- Produces human-readable output for metrics, statuses, and logs
SKILL.md
.github/skills/console-renderingView on GitHub ↗
---
name: console-rendering
description: Use Go struct tags to render styled terminal output in gh-aw.
---
# Console Rendering System Usage
Use this guide for the struct tag-based console rendering system.
## Struct Tag Support
Use the `console` struct tag to control rendering behavior:
- **`header:"Name"`** - Sets the display name for fields (used in both structs and tables)
- **`title:"Section Title"`** - Sets the title for nested structs, slices, or maps
- **`format:"type"`** - Sets the formatting type for the field value
- `format:number` - Formats integers as human-readable numbers (e.g., "1k", "1.2M")
- `format:cost` - Formats floats as currency with $ prefix (e.g., "$1.234")
- **`omitempty`** - Skips the field if it has a zero value
- **`"-"`** - Always skips the field
## Example Usage
```go
type Overview struct {
RunID int64 `console:"header:Run ID"`
Workflow string `console:"header:Workflow"`
Status string `console:"header:Status"`
Duration string `console:"header:Duration,omitempty"`
}
data := Overview{
RunID: 12345,
Workflow: "test-workflow",
Status: "completed",
Duration: "5m30s",
}
// Simple rendering
fmt.Print(console.RenderStruct(data))
// Output:
// Run ID : 12345
// Workflow: test-workflow
// Status : completed
// Duration: 5m30s
```
## Format Tag Examples
### Number Formatting
```go
type Metrics struct {
TokenUsage int `console:"header:Token Usage,format:number"`
Errors int `console:"header:Errors"`
}
data := Metrics{
TokenUsage: 250000,
Errors: 5,
}
// Renders as:
// Token Usage: 250k
// Errors : 5
```
### Cost Formatting
```go
type Billing struct {
Cost float64 `console:"header:Estimated Cost,format:cost"`
}
data := Billing{
Cost: 1.234,
}
// Renders as:
// Estimated Cost: $1.234
```
## Rendering Behavior
### Structs
Structs are rendered as key-value pairs with proper alignment.
### Slices
Slices of structs are automatically rendered as tables:
```go
type Job struct {
Name string `console:"header:Name"`
Status string `console:"header:Status"`
Conclusion string `console:"header:Conclusion,omitempty"`
}
jobs := []Job{
{Name: "build", Status: "completed", Conclusion: "success"},
{Name: "test", Status: "in_progress", Conclusion: ""},
}
fmt.Print(console.RenderStruct(jobs))
```
Renders as:
```
Name | Status | Conclusion
----- | ----------- | ----------
build | completed | success
test | in_progress | -
```
### Maps
Maps are rendered as markdown-style headers with key-value pairs.
### Special Type Handling
#### time.Time
`time.Time` fields are automatically formatted as `"2006-01-02 15:04:05"`. Zero time values are considered empty when used with `omitempty`.
#### Unexported Fields
The rendering system safely handles unexported struct fields by checking `CanInterface()` before attempting to access field values.
More from github/gh-aw
- agentic-workflow-designerConversational skill that interviews users to design new agentic workflows
- agentic-workflowsRoute gh-aw workflow design/create/debug/upgrade requests to the right prompts.
- awf-release-integratorUpgrade gh-aw to latest gh-aw-firewall release and identify follow-up spec tasks.
- checkout-credential-reviewReview code that performs git or gh operations against repository checkouts in gh-aw, checking that the right credentials are available at the right time and that sparseness, shallowness and credential-free factors are properly considered.
- copilot-reviewTeach Copilot how to plan, address, and respond to pull request review feedback.
- custom-agentsDefine and validate GitHub custom agent files, prompts, and examples.
- debugging-workflowsDebug gh-aw workflows using run logs, audits, and failure triage.
- developerCore developer rules and coding conventions for gh-aw changes.
- Dictation InstructionsInstructions for fixing speech-to-text errors and improving text quality in gh-aw documentation and workflows
- documentationWrite concise Diataxis docs for gh-aw with Starlight markdown conventions.