Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →streamlit/debugging-streamlit
Debug Streamlit frontend and backend changes using make debug with hot-reload.
Passed 22 of 22 test cases with the skill, and 6 of 22 without it.
and 22 more in the full report
16 fixed6 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
What quick command-line ripgrep search pattern checks for errors and exceptions in the backend log without opening the file?
| Checked | Without skill | With skill |
|---|---|---|
| Uses rg -i "error|exception" to search work-tmp/debug/latest/backend.log. | Missed | Passed |
The instructions your model reads when the skill loads.
make debug my_app.py
This starts both backend (Streamlit/Python) and frontend (Vite/React) with hot-reload. The app URL is printed on startup (default http://localhost:3001; 3000 is reserved for manual make frontend-dev; it may use 3002+ if other debug sessions are running). Avoid pinning VITE_PORT unless you have a specific hard requirement (last resort).
Hot-reload behavior:
frontend/ code are applied within seconds.lib/streamlit/) require restarting make debug.Each make debug run writes logs to a per-session directory under work-tmp/debug/ and updates work-tmp/debug/latest/ to point at the most recent session.
Because latest/* is a symlink, it can move if multiple debug sessions are starting/stopping concurrently—prefer using the session directory path printed by make debug when you need stable log references.
You can find the exact session directory in the make debug startup output under the Log files section.
| File | Content |
|---|---|
work-tmp/debug/latest/backend.log | Python print() statements, Streamlit logs, errors |
work-tmp/debug/latest/frontend.log | Browser console.log(), React errors, Vite output |
Logs are cleared at the start of each session and persist after exit for post-mortem analysis.
Log size warning: Logs can grow large during extended debugging sessions. Instead of reading entire log files, use rg to search for specific patterns:
# Search for specific debug messages
rg "DEBUG:" work-tmp/debug/latest/backend.log
# Search for errors (case-insensitive)
rg -i "error|exception|traceback" work-tmp/debug/latest/backend.log
# Search with context (3 lines before/after)
rg -C 3 "my_function" work-tmp/debug/latest/backend.log
# Search frontend logs for specific component
test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.