Verify document claims against codebase and Git evidence, then correct inaccuracies.
npx skills add https://github.com/ivanov-i/dots --skill visual-fact-check
Please help me install this Agent Skill. Skill: visual-fact-check Source: https://github.com/ivanov-i/dots/tree/main/codex/skills/visual-fact-check Command: npx skills add https://github.com/ivanov-i/dots --skill visual-fact-check
Verify factual accuracy of a document against the codebase and git evidence, then correct inaccuracies in place. Use when the user asks to validate HTML review pages, markdown plans/specs, or other code-claiming documents.
Provide the target document path and the repository reference to validate facts against the codebase.
High-intent search queries and answers about installing and using this skill.
To verify markdown specifications against a codebase, provide the target document path and the repository reference. The Skill compares the text against the repository and commit history to identify factual discrepancies and generates surgical in-place corrections grounded in code evidence.
Fact-checking a document with git evidence involves surfacing factual discrepancies between user-provided documents and the codebase by referencing commit history. It validates code-claiming documents like HTML review pages and markdown plans by grounding corrections in repository evidence.
Yes, you can validate HTML review pages against your repository. The Skill identifies factual discrepancies between the provided HTML document and the codebase, applies surgical corrections directly in place, and outputs a verification summary of what was changed.
The best way to correct documentation inaccuracies in place is to validate the document against the repository and commit history. The Skill applies surgical edits directly to the target document grounded in code evidence and generates a proof-of-work verification summary.
Yes, document verification works without external dependencies. The Skill operates independently to compare user-provided text against the repository and commit history to identify factual discrepancies and generate in-place corrections.
You should not use automated in-place corrections when your document does not make specific claims about the codebase or lacks a repository reference. The Skill requires a target document path and a repository to validate facts and generate grounded corrections.
agentic-inSelect inference paths, serving stacks, and benchmarking plans for ML models.
muddyrainValidate git commit messages against the Conventional Commits specification.
Kushal9889Sets up Husky git hooks to automate code quality checks and testing before commits.
rsmdtValidate implementations against documented specifications with structured compliance reporting.
