build-verify

Execute Rust and Android build verification gates for the SCMessenger project.

2|Updated Feb 6, 2026

Search Tags:#code quality #Android #Rust #build process #build verification

Ready to run

npx skills add https://github.com/Sovereign-Communication/SCMessenger --skill build-verify-sovereign-communication

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-verify
Source: https://github.com/Sovereign-Communication/SCMessenger/tree/main/.agents/skills/build-verify
Command: npx skills add https://github.com/Sovereign-Communication/SCMessenger --skill build-verify-sovereign-communication

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ensures the integrity of the SCMessenger build process by automatically running verification gates before any Rust or Android changes are considered final.

Core Features & Use Cases

Build Verification: Runs a series of gates to verify Rust (build/check/clippy/fmt/compile-gate) and Android (assembleDebug + RoleNavigationPolicyTest) builds.
Scope Selection: Allows users to select the specific gates to run (full, rust, android, wasm, compile_gate).
Fail Detection: Reports the PASS/FAIL summary and failing output if any gate fails, prompting action on the specific issue.

Quick Start

Run the build verification gates for the entire build by using the 'build-verify' skill with the 'full' argument: 'build-verify full'.

Frequently Asked Questions about build-verify

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

FAQPage Schema

How do I automate build verification gates for Rust and Android projects?▼

Automate build verification gates by executing scripts that check Rust and Android builds. The process verifies code quality and compatibility, running checks like clippy, fmt, assembleDebug, and compile-gate before changes are considered final.

What specific build checks are required to verify Rust and Android code quality?▼

To verify code quality, Rust requires build, check, clippy, fmt, and compile-gate checks, while Android requires assembleDebug and RoleNavigationPolicyTest. Running these gates ensures structural integrity and compatibility across the codebase.

Can I run verification gates for only the Rust or Android scope instead of the full build?▼

You can run verification gates for specific scopes by selecting rust, android, wasm, compile_gate, or full. This allows targeting individual platform builds rather than executing the entire verification suite.

What do I need to execute build verification scripts for my SCMessenger repository?▼

Executing build verification scripts requires access to the SCMessenger repository and execution permissions. These prerequisites allow the gates to run and verify both Rust and Android builds successfully.

How does fail detection work when a build verification gate reports an error?▼

Fail detection during build verification reports a PASS or FAIL summary. If a gate fails, it outputs the failing details to prompt action on the specific issue causing the build error.

Why does my Android RoleNavigationPolicyTest fail during the assembleDebug build verification?▼

RoleNavigationPolicyTest failures during assembleDebug indicate code quality or compatibility issues within the Android build. The verification gate reports the failing output to help you identify and resolve the specific issue.