crane-audit

Audit pull request diffs for Grove SDK compliance and pattern violations.

5|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/AutumnsGrove/Lattice --skill crane-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crane-audit
Source: https://github.com/AutumnsGrove/Lattice/tree/main/.claude/skills/crane-audit
Command: npx skills add https://github.com/AutumnsGrove/Lattice --skill crane-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that all code changes in pull requests adhere to Grove SDK compliance, coding conventions, and pattern violations, maintaining code quality and consistency across the project.

Core Features & Use Cases

  • Automated Compliance Checks: Scans pull request diffs against a comprehensive checklist of Grove SDK usage, security patterns, and best practices.
  • Detailed Reporting: Generates a structured report highlighting violations with specific file and line references, categorizing them as PASS, WARN, or FAIL.
  • Use Case: Before merging a new feature, use this Skill to automatically audit the pull request for adherence to all Grove development standards, preventing potential issues and ensuring a high-quality codebase.

Quick Start

Use the crane-audit skill to audit pull request number 342.

Frequently Asked Questions about crane-audit

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

FAQPage Schema
How do I audit a pull request for SDK compliance and pattern violations?

To audit a pull request for SDK compliance, you analyze code diffs against established standards to identify deviations and pattern violations. It generates a detailed compliance report categorizing issues as PASS, WARN, or FAIL with actionable remediation suggestions.

What is a PR compliance audit and how does it check code conventions?

A PR compliance audit systematically reviews pull request diffs against a checklist of SDK usage, security patterns, and best practices. It identifies deviations from established coding conventions and pattern violations to maintain code quality and consistency across the project.

How do I automatically check code diffs for security patterns before merging?

You automatically check code diffs for security patterns by running a compliance audit on the pull request before merging. The audit scans the changes against a comprehensive checklist of best practices, preventing potential issues and ensuring a high-quality codebase.

Does the code compliance audit report provide specific line references for violations?

Yes, the code compliance audit report provides specific file and line references for violations. It generates a structured report that highlights deviations from established standards, categorizing each finding as PASS, WARN, or FAIL to help you locate issues quickly.

Can I use this audit for pull requests that only contain minor convention deviations?

Yes, you can use this audit for any pull request regardless of change size. It analyzes code diffs to identify all deviations from established standards, ensuring even minor convention violations are caught and documented in the compliance report.