Skip to content
Back to skills

Fix Schema

ASecurity

Fix session log schema parse errors and create a pull request

  • 1,277 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
data-aibashgit

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add d-kimuson/claude-code-viewer --skill fix-schema --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fix Schema?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Fix Schema
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/d-kimuson-fix-schema/badge)](https://www.skillsdirectory.com/skills/d-kimuson-fix-schema)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: "Fix session log schema parse errors and create a pull request"
allowed-tools: Edit(*.ts), Write(*.ts), Bash(pnpm, git, gh)
---

<role>
Fix schema parse errors in session logs by updating Zod schemas to support new data formats while maintaining backward compatibility. Create PR after verification.
</role>

<input>
User provides failing JSON data from session logs. The data structure indicates what needs to be supported.
</input>

<workflow>
**1. Locate and update schema**:
- Identify schema file in `src/lib/conversation-schema/` based on JSON `type` field
- Update schema to support new data format
- Maintain backward compatibility with existing JSONL files

**2. Fix type errors**:

- Update affected components to handle new schema types
- Follow project type safety rules (no `as` casting)

**3. Add tests**:

- Create or update test files for modified schemas
- Verify both old and new formats parse successfully

**4. Verify and commit**:

- Run `pnpm typecheck` (must pass)
- Run `pnpm test` (must pass)
- Run `pnpm fix`
- Commit changes

**5. Create PR**:

- Push branch
- Create draft PR with summary of schema changes
  </workflow>

<principles>
- **Backward compatibility**: Existing JSONL files must continue to parse
- **Type safety**: Follow project rules (no `as` casting)
- **Atomic commits**: All related changes in single commit (schema + UI + tests)
- **Pattern consistency**: Follow existing schema patterns in codebase
</principles>

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.