pi-echo-test-status
Footer badge reflecting pass/fail from the last test/build bash command
Package details
Install pi-echo-test-status from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:pi-echo-test-status- Package
pi-echo-test-status- Version
0.1.0- Published
- Aug 15, 2026
- Downloads
- 145/mo · 10/wk
- Author
- hegdesumanth.dev
- License
- unknown
- Types
- extension
- Size
- 4.8 KB
- Dependencies
- 0 dependencies · 1 peer
Pi manifest JSON
{
"extensions": [
"."
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
pi-echo-test-status
A footer badge reflecting pass/fail from the last test/build bash command (✓ test / ✗ build).
Design note
Uses the bash tool's own isError field on the tool_result event as the pass/fail source, not output text-sniffing. Verified against the installed package's actual bash.js rather than assumed: the bash tool throws when the exit code is non-zero (instead of manually setting isError itself), and Pi's generic tool-execution wrapper converts that thrown error into isError: true upstream — so by the time this extension sees the event, isError already accurately reflects the real exit code, the same authoritative source pi-echo-ci uses for tool_execution_end.
Command matching is a pattern list covering npm/yarn/pnpm, cargo, go, pytest, mvn, make, and gradle — necessarily incomplete for anything not on that list, stated plainly rather than implying full coverage. Each pattern carries its own test/build label rather than re-deriving it from the command text separately — found via testing, not assumed correct: a word-boundary re-derivation mislabeled pytest -v as "check" instead of "test", since "test" isn't its own word inside "pytest". Pairing the label with the pattern that matched avoids that whole class of bug.
Usage
No configuration — install it and the badge appears in the footer after the next matching test/build command runs.