菜单
Cut a new FireCrasher library release — bump the version, sync the README and ABI baseline, verify, and tag for JitPack. Use when asked to "release", "publish", "cut a version", or "bump to x.y.z".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Add or update a Robolectric JVM unit test for the FireCrasher library. Use when changing recovery logic, crash handling, back-stack counting, exit-info reporting, or the recovery-state codec, and a test should cover it.
Inspect FireCrasher's recovery level and show custom recovery UX (loading dialog, toast, snackbar) or force a specific recovery level. Use when tailoring what the user sees during recovery, or reacting differently to occasional vs. repeated crashes.
Report native crashes, ANRs, and low-memory kills that FireCrasher's in-process handler cannot catch, using ApplicationExitInfo on API 30+. Use when you need a complete crash picture, or "why don't I get reports for native crashes / ANRs".
Add the FireCrasher crash-recovery library to an Android app and install it in the Application class. Use when integrating FireCrasher, setting up crash recovery, or when "app crashes should recover instead of closing".
Forward FireCrasher-caught exceptions to a crash reporter (Crashlytics, Sentry, etc.) while still recovering the app. Use when wiring crash reporting, logging non-fatals, or "make sure we still get crash reports after recovery".
Run the full local build that mirrors CI for FireCrasher — unit tests, Android lint, and the ABI baseline comparison. Use before pushing or opening a PR, or whenever asked to "run the tests", "check the build", or "verify it compiles".
| name | release |
| description | Cut a new FireCrasher library release — bump the version, sync the README and ABI baseline, verify, and tag for JitPack. Use when asked to "release", "publish", "cut a version", or "bump to x.y.z". |
FireCrasher is distributed through JitPack, which builds from a git tag —
there is no separate publish pipeline in this repo. A release is: get the
version and metadata in sync, verify, commit, and tag. JitPack does the rest
(jitpack.yml pins JDK 21; coordinates are remapped to
com.github.osama-raddad:FireCrasher:<tag>).
The current version is 3.0.0. Pick the new version with semantic versioning:
a breaking public API change (anything that alters firecrasher/api/firecrasher.api
incompatibly) is a major bump.
Land the code first. All feature/fix work for the release should already
be merged or staged. Run the run-checks skill and confirm green.
Bump VERSION_NAME in firecrasher/build.gradle (the
version = project.findProperty('VERSION_NAME') ?: '3.0.0' fallback in the
publishing block). Set it to the new version.
Update README.md:
implementation 'com.github.osama-raddad:FireCrasher:<new>'.Sync the ABI baseline. If the public API changed, run the
update-abi-baseline skill so firecrasher/api/firecrasher.api matches.
apiCheck must pass.
Verify the whole thing once more:
./gradlew build --stacktrace
Commit the version bump, README, and any baseline change together, e.g.
Release 2.2.0.
Tag and push (the tag is what JitPack builds):
git tag <new> # e.g. git tag 2.2.0 — match the README's coordinate
git push origin <new>
Tag names become the JitPack version verbatim, so the tag must equal the version string in the README install snippet.
Confirm the JitPack build at https://jitpack.io/#osama-raddad/FireCrasher
resolves the new version (first fetch triggers the build).
app/ module has its own versionCode/versionName; it is not
published and does not need to track the library version.firecrasher.api by hand to force a release — regenerate it with
apiDump.