desktop app to browse and analyze your Claude Code conversation history
Claude Code History Viewer is a desktop application and headless web server for browsing, searching, and analyzing conversation histories from many AI coding assistants. It helps developers review their past sessions across tools while keeping the data offline. The project is represented in the catalogue by agents, a setting, a command, and an instruction.
jhlee0409/claude-code-history-viewer
Agent Claude Code
A read-only reviewer for evaluating whether a pull request, a proposed set of code changes, is ready to merge into a project. It checks the request's target branch, changed files, code quality, merge status, and available automated checks.
jhlee0409/claude-code-history-viewer
Agent Claude Code
Verifies translation-key completeness and integrity across all 5 languages. Use after any change that touches src/i18n/locales/, when reviewing a PR that adds user-facing strings, or when the user says "check i18n", "are translations in sync?", "i18n 검증". Confirms every key added in en/ exists in ko/ ja/ zh-CN/…
jhlee0409/claude-code-history-viewer
Agent Claude Code
A read-only helper for triaging GitHub issues, which are reports or requests attached to a code project. It reads issues in Chinese, Korean, Japanese, or English, classifies them, suggests an existing label, and drafts a reply.
jhlee0409/claude-code-history-viewer
Agent Claude Code
A read-only review guide for pull requests that add support for a new AI coding assistant. It compares the new provider with existing provider implementations and checks how the assistant's history is found across operating systems.
jhlee0409/claude-code-history-viewer
Agent Claude Code
An agent for running a frontend release quality check on the claude-code-history-viewer project. The check covers TypeScript, tests, linting, and translation-key validation.
jhlee0409/claude-code-history-viewer
Agent Claude Code
Architecture specialist for claude-code-history-viewer's rust code. Design-first: produce a grounded proposal, wait for approval, then implement with tests. Use for refactors, restructuring, or deepening the rust architecture — not for crude surface patches.
jhlee0409/claude-code-history-viewer
Agent Claude Code
Detects drift between the Tauri desktop command surface and the Axum WebUI server surface. Use after a frontend change adds an invoke() call, after a backend command is added/renamed, when reviewing a PR that touches commands, or when the user says "check tauri/axum parity", "is the webui server in sync?". A command…
jhlee0409/claude-code-history-viewer
Agent Claude Code
Architecture specialist for claude-code-history-viewer's typescript code (react). Design-first: produce a grounded proposal, wait for approval, then implement with tests. Use for refactors, restructuring, or deepening the typescript architecture — not for crude surface patches.
jhlee0409/claude-code-history-viewer
Agent Claude Code
Verifies a frontend UI change actually works in a real rendered view before it is reported done — not jsdom, not a snapshot, the real thing. Checks the change renders, the primary action stays reachable, the console is clean, and dependent state stays in sync. Use after a UI change in claude-code-history-viewer…
jhlee0409/claude-code-history-viewer
Agent
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
jhlee0409/claude-code-history-viewer
Agent
Repo: jhlee0409/claude-code-history-viewer. Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
jhlee0409/claude-code-history-viewer
Agent
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: