Fix SchemaSAFE
A full-featured web-based Claude Code client that provides complete interactive functionality for managing Claude Code projects
Overview
A full-featured web-based Claude Code client that provides complete interactive functionality for managing Claude Code projects
3325aa7ccd00OBSERVED · 2026-10-09What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- 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>
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (2)
.codex/skills
Gates applied: no_behavioural_pass.
3325aa7ccd00full audit observations/trust-audit/skill/d-kimuson__fix-schema.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 3325aa7ccd00 | SAFE | B | 89 | first audit |
Questions
What does the Fix Schema skill do?
A full-featured web-based Claude Code client that provides complete interactive functionality for managing Claude Code projects
Is Fix Schema safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Fix Schema access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (3325aa7ccd00), read on 2026-10-09. The repository is watched, and a new audit runs when it changes — this is the first audit.