committing-android-changes

Pass

Audited by Runlayer on Mar 6, 2026

Risk Level: LOW
Scan Summary
Max Score
71%
Files
1
Flagged
1
Chunks
1
Flagged Files (1)
committing-android-changes/SKILL.mdLOW
71.0%

Risky tool definition detected

**Verify no generated files**: No build outputs, `.idea/` changes, or generated code --- ## What NOT to Commit - `.env` files or `user.properties` with real tokens - Credential files or signing keystores - Build outputs (`build/`, `*.apk`, `*.aab`) - IDE-specific files (`.idea/` changes, `*.iml`) - Large binary files --- ## Staging Best Practices - **Stage specific files** by name rather than `git add -A` or `git add .` - Put each file path on its own line for readability: ```bash git add \ path

Audit Metadata
Max File Score
71%
Classification
UNKNOWN_SERVER
Files Scanned
1
Files Flagged
1
Chunks Analyzed
1
Analyzed
Mar 6, 2026, 11:29 AM
Security Audit — runlayer — committing-android-changes