Imported from vabpf/spend-sense (AGENTS.md). Install upstream with npx skills add vabpf/spend-sense. Copyright stays with the author.

SpendSense — Android App

Build & Install

./gradlew assembleDebug
/mnt/d/Apps/Android/Sdk/platform-tools/adb.exe install app/build/outputs/apk/debug/app-debug.apk

./gradlew assembleRelease
cp app/build/outputs/apk/release/app-release.apk /mnt/c/Users/vuong/Downloads/SpendSense.apk

Note: Adjust the adb path for your environment (e.g., /mnt/d/Apps/Android/Sdk/platform-tools/adb.exe on WSL with Windows).

Project Structure

• Platform: Android (Kotlin, Jetpack Compose, Material 3)
• Architecture: Clean Architecture with Hilt DI, Room database
• Modules: Single-module Android app (app/)

GitNexus — Code Intelligence

This project is indexed by GitNexus as spend-sense (1077 symbols, 2377 relationships, 73 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.

If any GitNexus tool warns the index is stale, run npx gitnexus analyze in terminal first.

Always Do

• MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run gitnexus_impact({target: "symbolName", direction: "upstream"}) and report the blast radius to the user.
• MUST run gitnexus_detect_changes() before committing to verify your changes only affect expected symbols and execution flows.
• MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.

CLI

GitNexus — Code Intelligence

This project is indexed by GitNexus as spend-sense (2226 symbols, 4676 relationships, 113 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.

If any GitNexus tool warns the index is stale, run npx gitnexus analyze in terminal first.

Always Do

• MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run gitnexus_impact({target: "symbolName", direction: "upstream"}) and report the blast radius (direct callers, affected processes, risk level) to the user.
• MUST run gitnexus_detect_changes() before committing to verify your changes only affect expected symbols and execution flows.
• MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
• When exploring unfamiliar code, use gitnexus_query({query: "concept"}) to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.
• When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use gitnexus_context({name: "symbolName"}).

Never Do

• NEVER edit a function, class, or method without first running gitnexus_impact on it.
• NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
• NEVER rename symbols with find-and-replace — use gitnexus_rename which understands the call graph.
• NEVER commit changes without running gitnexus_detect_changes() to check affected scope.

Resources

CLI