auditor

To perform an independent code audit against change logs, you triangulate the intended purpose from the logs against the actual code implementation, verifying data flow, API consistency, and cross-file integrity. The auditor skill executes this verification independently without prior session knowledge.

Triangulation verification in code review is the process of comparing the actual code implementation against documented change logs and initial plans to ensure the changes fulfill the documented intent without introducing unintended side effects or deviations.

To check for ripple effects and security risks before merging a bug fix, you apply defensive auditing to the code changes, which verifies data flow, enforces defensive checks for performance and security, and ensures pragmatic testing strategy adherence.

Yes, the code auditor requires read, grep, and bash tools for file analysis and code inspection. These tools enable the skill to perform rigorous verification of data flow, cross-file integrity, and potential ripple effects.

The best way to verify API consistency and cross-file integrity is to use an independent code auditor that triangulates change logs against actual code implementation, leveraging read, grep, and bash tools to inspect data flow and enforce defensive checks.

You should not use an independent code auditor when you lack a change log or documented intent to verify against, as the triangulation verification process relies on comparing actual code implementation against these documented plans to detect deviations and side effects.