history-portability
>
git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor /tmp/history-portability && cp -r /tmp/history-portability/plugins/ccam-platform/skills/history-portability ~/.claude/skills/history-portabilitySKILL.md
# History Portability ## Provider History 1. Read provider-specific paths and limits: `ccam import guide --provider claude|codex`. 2. Rescan the configured provider home: `ccam import rescan --provider <provider>`. 3. Scan an existing directory: `ccam import path /absolute/path --provider <provider>`. 4. For file or archive upload, use the app or MCP `dashboard_upload_history_files`. ## Full Dashboard Backup ```bash ccam export ccam-export.json ccam import-data ccam-export.json ``` Restore is idempotent and non-destructive. Existing sessions are skipped as a whole. New sessions bring agents, events, token usage, and workflows. Independent run, rule, and pricing rows are inserted only when absent. Verify session counts, representative transcripts, token totals, cost, workflow runs, alert rules, and both Claude and GPT pricing after restore.
Operate and maintain the local MCP server for this repository. Use for MCP tool updates, policy-guard changes, host configuration, and MCP runtime troubleshooting.
Run release-readiness checks for this repository. Use when validating docs, scripts, verification coverage, and operational safety before merge or release.
Understand this repository quickly before making changes. Use for architecture discovery, ownership mapping, command selection, and initial implementation planning.
Review backend route and hook logic for regressions, data integrity risks, and missing tests.
Review React UI changes for behavior regressions, state consistency, and UX breakage.
Review MCP server changes for tool safety, schema quality, and host integration correctness.
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.
Operate and maintain the local MCP server for this project. Use when creating MCP host config, troubleshooting tool connectivity, modifying tool domains, or adjusting safety policy flags.