audit-field-mapping

Compare field names across dialog forms, mapper configurations, and database tables.

Updated May 30, 2026

Search Tags:#code review #audit #bug detection #field mapping #database consistency

Ready to run

npx skills add https://github.com/buitrankimlong/thongtincty --skill audit-field-mapping

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-field-mapping
Source: https://github.com/buitrankimlong/thongtincty/tree/main/.claude/skills/audit-field-mapping
Command: npx skills add https://github.com/buitrankimlong/thongtincty --skill audit-field-mapping

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Detects "silent save failure" bugs by comparing field names across forms, mappers, and database tables, ensuring data consistency.

Core Features & Use Cases

Systematic Audit: Identifies mismatches in field names across the dialog, mapper, and database, preventing silent bugs.
Use Cases: Applicable when adding or editing forms, post-bug reports, or before committing database changes.
Batch Audit: Scans all dialog/service pairs for mismatches, providing comprehensive reports.

Quick Start

Run the audit for the 'ContactDialog' ↔ 'contactsService' ↔ 'contacts' trio.

Frequently Asked Questions about audit-field-mapping

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

FAQPage Schema

How do I detect field mapping mismatches between forms, services, and database tables?▼

Detect field mapping mismatches by cross-checking field names across dialog forms, mapper configurations, and database tables. This audit identifies discrepancies in the data lifecycle, preventing silent save failures and ensuring database consistency.

Why does my form save data silently fail to persist in the database?▼

Silent save failures occur when field names mismatch across the dialog, service mapper, and database table. Auditing this trio for naming discrepancies exposes where data drops out of the lifecycle, allowing you to fix the inconsistencies causing the silent bugs.

What is the best way to audit database consistency before a migration?▼

The best way to audit database consistency before migration is running a batch scan of all dialog and service pairs. This systematically identifies field naming mismatches across the entire data lifecycle, generating comprehensive reports of discrepancies to fix.

Can I batch audit all dialog and service pairs for field name discrepancies?▼

Yes, you can batch audit all dialog and service pairs to find field name discrepancies. The batch audit scans every form, mapper configuration, and database table trio, providing comprehensive reports of mismatches that could cause silent data persistence failures.

When should I run a field mapping audit during development?▼

Run a field mapping audit when adding or editing dialog forms, analyzing post-bug reports, or before committing database changes. Cross-checking multiple data sources at these stages applies specific audit rules to catch silent save failures early.

Do I need specific dependencies to cross-check dialog forms against database tables?▼

No specific dependencies are required to cross-check dialog forms against database tables. The audit applies specific rules directly to your codebase to identify discrepancies across the dialog, mapper, and database trio without external tooling.