skills.rest
accelerate-data
accelerate-dataOFFICIAL
Explore all skills by this author →
WebsiteGitHub

reviewing-diagnostics

Group per-table catalog diagnostics by root cause and apply fixes.

3|Updated Feb 27, 2026
Search Tags:#audit#migration#catalog#diagnostics#artifact#data-quality#per-table
One-click install
npx skills add https://github.com/accelerate-data/migration-utility --skill reviewing-diagnostics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewing-diagnostics
Source: https://github.com/accelerate-data/migration-utility/tree/main/skills/reviewing-diagnostics
Command: npx skills add https://github.com/accelerate-data/migration-utility --skill reviewing-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and fix active catalog diagnostics for a single table to correct wrong or stale facts and enable safe migrations.

Core Features & Use Cases

  • Identify all active diagnostics for the specified table
  • Group issues by root cause and apply catalog-level fixes or generate a reviewed-warning artifact
  • Re-run the batch-plan to verify diagnostics are resolved and provide next steps

Quick Start

Run the review workflow for a specific table by loading its diagnostics and catalog context, then apply fixes or write a reviewed-warning artifact.

Frequently Asked Questions about reviewing-diagnostics

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

FAQPage Schema
How do I fix active catalog diagnostics for a specific table?▼

To fix active catalog diagnostics for a specific table, you group the identified issues by root cause and apply catalog-level fixes or generate a reviewed-warning artifact to correct stale or incorrect facts.

What is the best way to resolve stale catalog facts before a data migration?▼

Resolving stale catalog facts before a data migration involves reviewing per-table diagnostics, applying catalog-level corrections to fix incorrect data, and re-running the batch-plan to verify all issues are resolved.

How do I review per-table diagnostics and group issues by root cause?▼

Reviewing per-table diagnostics requires loading the table's diagnostic rules and catalog context, identifying active issues, and grouping them by root cause to systematically apply catalog-level fixes or write reviewed warnings.

Do I need access to catalog files to correct incorrect diagnostic artifacts?▼

Yes, correcting incorrect diagnostic artifacts requires direct access to catalog files and diagnostic rules to apply catalog-level fixes or write reviewed-warning artifacts for the specified table.

How do I verify that catalog-level fixes have resolved active diagnostics?▼

To verify catalog-level fixes have resolved active diagnostics, re-run the batch-plan after applying corrections or generating warnings to confirm the diagnostics are cleared and obtain next steps.

When should I generate a reviewed-warning artifact instead of modifying catalog files?▼

You should generate a reviewed-warning artifact instead of modifying catalog files when the per-table diagnostics identify issues that require acknowledgment and warning generation rather than direct catalog fact corrections.

Related Skills

Explore More Data & Analytics Skills→
N0nkiN0nki

nvim-diagnostics

Extract Neovim LSP diagnostics and group code issues by severity.

Community
Intermediate
MrHan-YdMrHan-Yd
1

trellis-continue

Load current Trellis task context and determine the next actionable step.

Community
Intermediate
DKSangDKSang
2

des-create-story

Convert an Epic Catalog into a traceable Story Catalog with acceptance criteria.

Community
Intermediate
designnotdrumdesignnotdrum
3

managing-memory

Store structured memories with facts, reasons, sentiment, and implications.

Community
Basic