원클릭으로
jqschema
JSON schema discovery utility that extracts structure and type information from JSON data
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
JSON schema discovery utility that extracts structure and type information from JSON data
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Documentation Brief description for SEO and navigation
Go through all review comments on the current branch's PR, check if each is still valid, fix valid issues, reply to every comment, and resolve all review threads via the GitHub API.
Golang code style, formatting and conventions. Use when writing code, reviewing style, configuring linters, writing comments, or establishing project standards.
Golang concurrency patterns. Use when writing or reviewing concurrent Go code involving goroutines, channels, select, locks, sync primitives, errgroup, singleflight, worker pools, or fan-out/fan-in pipelines. Also triggers when you detect goroutine leaks, race conditions, channel ownership issues, or need to choose between channels and mutexes.
Idiomatic context.Context usage in Golang — creation, propagation, cancellation, timeouts, deadlines, context values, and cross-service tracing. Apply when working with context.Context in any Go code.
Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/list/heap/ring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing Go data structures, implementing generic containers, using container/ packages, unsafe or weak pointers, or questioning slice/map internals.
| name | jqschema |
| description | JSON schema discovery utility that extracts structure and type information from JSON data |
| tools | {"bash":["jq *","/tmp/gh-aw/jqschema.sh","git"]} |
| steps | [{"name":"Setup jq utilities directory","run":"mkdir -p /tmp/gh-aw\ncp \"$GITHUB_WORKSPACE/.github/skills/jqschema/jqschema.sh\" /tmp/gh-aw/jqschema.sh\nchmod +x /tmp/gh-aw/jqschema.sh\n"}] |
A utility script is available at /tmp/gh-aw/jqschema.sh to help you discover the structure of complex JSON responses.
Generate a compact structural schema (keys + types) from JSON input. This is particularly useful when:
# Analyze a file
cat data.json | /tmp/gh-aw/jqschema.sh
# Analyze command output
echo '{"name": "test", "count": 42, "items": [{"id": 1}]}' | /tmp/gh-aw/jqschema.sh
# Analyze GitHub search results
gh api search/repositories?q=language:go | /tmp/gh-aw/jqschema.sh
The script transforms JSON data by:
Input:
{
"total_count": 1000,
"items": [
{"login": "user1", "id": 123, "verified": true},
{"login": "user2", "id": 456, "verified": false}
]
}
Output:
{"total_count":"number","items":[{"login":"string","id":"number","verified":"boolean"}]}
Use this script when:
perPage: 1 and pipe through schema minifier first)Example workflow for GitHub search tools:
# Step 1: Get schema with minimal data (fetch just 1 result)
# This helps understand the structure before requesting large datasets
echo '{}' | gh api search/repositories -f q="language:go" -f per_page=1 | /tmp/gh-aw/jqschema.sh
# Output shows the schema:
# {"incomplete_results":"boolean","items":[{...}],"total_count":"number"}
# Step 2: Review schema to understand available fields
# Step 3: Request full data with confidence about structure
# Now you know what fields are available and can query efficiently
Using with GitHub MCP tools:
When using tools like search_code, search_issues, or search_repositories, pipe the output through jqschema to discover available fields:
# Save a minimal search result to a file
gh api search/code -f q="jq in:file language:bash" -f per_page=1 > /tmp/sample.json
# Generate schema to understand structure
cat /tmp/sample.json | /tmp/gh-aw/jqschema.sh
# Now you know which fields exist and can use them in your analysis