gt:analyze-har
HAR Analyzer
Token-efficient HAR analysis. Uses a reference system - large data shown once gets a ref ID, subsequent views show [ref:ID] + preview instead of repeating.
Critical Rule
NEVER cat, jq, or directly read a HAR file. Always use tools har-analyzer commands. Raw HAR reading wastes 10-100x more tokens.
Optimal Workflow
1. tools har-analyzer load <file.har> # Parse + dashboard (always start here)
2. tools har-analyzer list --status 4xx # Filter to what matters
3. tools har-analyzer domain <domain> # Drill into specific API
4. tools har-analyzer show e14 # Detail for one entry
5. tools har-analyzer show e14 --raw # Full body/headers if needed
6. tools har-analyzer expand e14.rs.body # Re-show a referenced value
More from genesiscz/genesistools
genesis-tools:github
|
18genesis-tools:codebase-analysis
Deep codebase analysis without cluttering main session
16gt:claude-history
Find or reference a past Claude Code conversation — fixes, decisions, or discussions from earlier sessions ("you helped me fix", "we debugged", "I remember asking"). Locate sessions by topic, file, or date. Not for codebase/git/Slack history.
2gt:github
|
1debugging-master
|
1gt:git-rebaser
Guided git rebase cascade for branch hierarchies. Use when rebasing a parent feature branch onto master/main and then updating child branches. Triggers on "rebase branches", "cascade rebase", "rebase onto master", "update child branches after rebase", "rebase feature branch hierarchy", "git rebaser". Handles reflog lookup, --onto mechanics, commit reporting, and user confirmation before any destructive action.
1