One-click install
npx skills add https://github.com/Arcanada-one/datarim --skill datarim-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: datarim-doctor
Source: https://github.com/Arcanada-one/datarim/tree/main/skills/datarim-doctor
Command: npx skills add https://github.com/Arcanada-one/datarim --skill datarim-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Datarim operational files can drift over time—breaking the expected thin-index formats, losing canonical task descriptions, or accumulating deprecated sections like progress logs and archive blocks. This Skill provides a rigorous, data-loss-safe self-heal that validates the repository layout and migrates it back to the canonical schema.

Core Features & Use Cases

  • Schema conformance and validation: Enforces the canonical one-liner index formats for tasks and backlog entries, plus strict contracts for active context mirroring.
  • 6-pass, idempotent migration: Converts legacy block-style task descriptions into per-task description files, rewrites operational indexes, retires deprecated files/sections, and migrates archive history into documentation.
  • Conflict handling with safety guarantees: Resolves archive-file conflicts under a configurable policy and ensures atomicity with pre-write backups and restore-on-error.
  • Use Case: Fix a repository that has accumulated manual edits to tasks.md/backlog.md/activeContext.md, including legacy headings and archive sections, so that commands like /dr-archive and /dr-status work reliably again.

Quick Start

Run datarim-doctor in fix mode to validate and migrate the Datarim repository back to the canonical schema.

Frequently Asked Questions about datarim-doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I normalize Datarim schemas that have drifted from the canonical format?

To normalize Datarim schemas, this Skill runs a 6-pass migration that rewrites operational indexes, converts legacy block-style task descriptions into per-task files, and restores the canonical thin-index format.

What is the safest way to migrate legacy archive sections in a Datarim repository?

Migrating legacy archive sections safely requires a data-loss-safe process with pre-write backups and restore-on-error invariants. This Skill applies atomic per-file rewrites to migrate archive history into documentation reliably.

How do I fix manual edits in tasks.md and backlog.md that break Datarim commands?

Fixing manual edits in tasks.md and backlog.md involves validating the repository layout against strict schema conformance rules. This Skill retires deprecated sections and enforces canonical one-liner index formats so commands like /dr-archive work again.

Does the Datarim schema migration handle conflicts in archive files?

Yes, Datarim schema migration resolves archive-file conflicts using a configurable policy with deterministic conflict resolution, ensuring that archival documents are normalized without losing historical data.

Can I run this schema normalization repeatedly without causing duplicate migrations?

Yes, you can run this schema normalization repeatedly because the 6-pass migration is idempotent, meaning applying the fixes multiple times produces the same canonical repository state without duplicating entries or causing errors.

When should I use a self-heal workflow for Datarim operational files?

You should use a self-heal workflow when operational files have accumulated deprecated sections like progress logs and archive blocks, or when active context mirroring contracts break and commands such as /dr-status fail to execute reliably.