personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[Sprint 10] feat: Create data-integrity-audit.md skill #373

New Issue
Closed
opened 2026-02-02 06:20:55 +00:00 by lmiranda · 0 comments
lmiranda commented 2026-02-02 06:20:55 +00:00
Owner
Copy Link

Summary

Create the foundational skill that defines what "data valid" means for the data-platform domain. This skill is loaded by the data-advisor agent and provides audit rules, severity classification, scanning strategy, and report templates.

Wiki Reference: Sprint 10 Implementation

File to Create

plugins/data-platform/skills/data-integrity-audit.md

Required Sections

  1. Purpose - When and why to audit data integrity
  2. What to Check - Check categories table (Schema Validity, dbt Project Health, Lineage Integrity, Data Type Consistency, PostGIS Compliance, Query Safety)
  3. Common Violations - Detection patterns for each violation type
  4. Severity Classification - FAIL/WARN/INFO levels with gate behavior
  5. Scanning Strategy - How to scan dbt projects, PostgreSQL schemas, DataFrames, Python code
  6. Report Template - Gate mode (compact) and Review mode (detailed) templates

MCP Tools Referenced

PostgreSQL: pg_tables, pg_columns, pg_schemas
dbt: dbt_parse, dbt_compile, dbt_test, dbt_ls, dbt_lineage
PostGIS: st_tables, st_geometry_type, st_srid, st_extent
pandas: describe, head, list_data

Acceptance Criteria

  • Skill file created with proper frontmatter
  • All 6 check categories documented with MCP tools
  • Common violations table with detection patterns
  • Severity classification matches viz-platform pattern (FAIL blocks gate, WARN/INFO don't)
  • Gate mode and review mode report templates defined
  • Scanning strategy covers dbt, PostgreSQL, PostGIS, pandas, Python code
## Summary Create the foundational skill that defines what "data valid" means for the data-platform domain. This skill is loaded by the `data-advisor` agent and provides audit rules, severity classification, scanning strategy, and report templates. **Wiki Reference:** [Sprint 10 Implementation](https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/wiki/Change-V5.7.0%3A-Data-Platform-Domain-Advisory-%28Sprint-10-Implementation%29) ## File to Create `plugins/data-platform/skills/data-integrity-audit.md` ## Required Sections 1. **Purpose** - When and why to audit data integrity 2. **What to Check** - Check categories table (Schema Validity, dbt Project Health, Lineage Integrity, Data Type Consistency, PostGIS Compliance, Query Safety) 3. **Common Violations** - Detection patterns for each violation type 4. **Severity Classification** - FAIL/WARN/INFO levels with gate behavior 5. **Scanning Strategy** - How to scan dbt projects, PostgreSQL schemas, DataFrames, Python code 6. **Report Template** - Gate mode (compact) and Review mode (detailed) templates ## MCP Tools Referenced PostgreSQL: `pg_tables`, `pg_columns`, `pg_schemas` dbt: `dbt_parse`, `dbt_compile`, `dbt_test`, `dbt_ls`, `dbt_lineage` PostGIS: `st_tables`, `st_geometry_type`, `st_srid`, `st_extent` pandas: `describe`, `head`, `list_data` ## Acceptance Criteria - [ ] Skill file created with proper frontmatter - [ ] All 6 check categories documented with MCP tools - [ ] Common violations table with detection patterns - [ ] Severity classification matches viz-platform pattern (FAIL blocks gate, WARN/INFO don't) - [ ] Gate mode and review mode report templates defined - [ ] Scanning strategy covers dbt, PostgreSQL, PostGIS, pandas, Python code
lmiranda added the Type/Feature label 2026-02-02 06:20:55 +00:00
lmiranda added this to the Sprint 10 - Domain Advisory Pattern (data-platform) milestone 2026-02-02 06:21:39 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label Type/Feature
Milestone
No items
No Milestone Sprint 10 - Domain Advisory Pattern (data-platform)
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#373
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?