Menu
Fetches unresolved Sentry issues and maps stack traces to local codebase for ShizukuPlus.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/thejaustin/ShizukuPlus --skill sentry-auditThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Guidelines and instructions for developing, testing, and troubleshooting ShizukuPlus (an enhanced Shizuku manager with OneUI 8+ fixes, Dhizuku mode, and Plus APIs).
Shizuku+ codebase integrity checks. Use before pushing or committing to ensure no common build-breaking issues (CMake versions, missing imports, Java/Kotlin interop) exist.
Automates running Android Lint and repairing errors/warnings in the codebase.
Based on SOC occupation classification
Showing SKILL.md
| name | sentry-audit |
| description | Fetches unresolved Sentry issues and maps stack traces to local codebase for ShizukuPlus. |
| license | Complete terms in LICENSE |
| metadata | {"author":"Google LLC","keywords":["sentry","audit","crashes","debugging"]} |
This skill minimizes token usage while extracting actionable crash data from the Sentry REST API and mapping it to the local codebase.
Fetch Unresolved Issues:
Run a curl command against the Sentry API to fetch unresolved issues. Extract ONLY the id, shortId, title, and culprit.
curl -s -H 'Authorization: Bearer <SENTRY_TOKEN>' "https://sentry.io/api/0/projects/af-developments/shizukuplus/issues/?query=is:unresolved" | jq -c '.[] | {id, shortId, title, culprit}'
Note: Do NOT fetch the full JSON dump into context; it is massive and wastes tokens.
Fetch Stack Trace for Top Issue: Pick the highest priority issue ID and fetch its exact stack trace.
curl -s -H 'Authorization: Bearer <SENTRY_TOKEN>' "https://sentry.io/api/0/issues/<ISSUE_ID>/events/latest/" | jq -r '.entries[] | select(.type=="exception") | .data.values[].stacktrace.frames[] | "\(.filename):\(.lineNo) - \(.function)"'
Note: Using jq filters the payload down to just filename, line number, and function, drastically saving context space.
Map to Codebase:
Use the grep_search tool to find the corresponding file in manager/src/main/ based on the .filename from the stack trace.
Repair:
Analyze the bug and use the replace_file_content or multi_replace_file_content tool to patch the error.
Resolve via API: Once pushed to master, automatically resolve the issue on Sentry:
curl -s -X PUT -H 'Authorization: Bearer <SENTRY_TOKEN>' -H "Content-Type: application/json" -d '{"status":"resolved"}' "https://sentry.io/api/0/issues/<ISSUE_ID>/"