Loading…
How dualdb validates that converted code still builds, and how it reports what was actually validated. Use when running or interpreting a build, when mapping a diagnostic to a finding, when choosing a build tier, or when writing the build line of the report. Never claim a tier you did not reach.
build-validation is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Build validation Be explicit and honest about what was actually validated. Report the tier reached; never claim more. ## When to use Running the baseline or p. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding build-validation to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install omkarnade-sf/DualDb_Migration_Without_AIReview the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
# Build validation Be explicit and honest about what was actually validated. Report the tier reached; never claim more. ## When to use Running the baseline or post-conversion build