ops-check-logs_skill
- TypeScript
1
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill codyswanngt/lisa --skill ops-check-logs- SKILL.md6.5 KB
Overview
This skill helps you locate, tail, and search application logs across local processes, browser consoles, React Native devices, and remote AWS CloudWatch. It centralizes common workflows for filtering, error hunting, and live tailing so you can quickly identify runtime issues across frontend and backend environments.
How this skill works
The tool discovers log entry points by reading backend scripts, environment files, and known project paths to find log and watch commands, function names, and Sentry DSNs. It supports capturing stdout from local services, browser console output (via Playwright or DevTools), device logs for iOS/Android, and CloudWatch access through Serverless scripts or direct AWS CLI commands. Results are reported in a consistent table format with source, timestamp, level, context, and message plus a summary of errors and patterns.
When to use it
- Debugging runtime errors in local frontend or backend processes
- Capturing browser console and failed network requests during UAT
- Inspecting React Native device or simulator logs for JS/native issues
- Tailing production function logs in CloudWatch to investigate incidents
- Filtering recent errors across environments to triage recurring failures
Best practices
- Set BACKEND_DIR in local settings if backend is outside the default path
- Use logs:watch scripts or aws logs tail for live follow mode instead of re-running queries
- Correlate Sentry DSN from .env files with CloudWatch traces when available
- Capture browser logs programmatically with Playwright for repeatable UAT
- Filter by error level and time window to reduce noise when searching production logs
Example use cases
- Tail a Lambda function in staging: set FUNCTION_NAME and run logs:watch:staging
- Reproduce a client-side crash and capture console + network failures via Playwright
- Collect Android JS logs using adb logcat -s ReactNativeJS when a device shows UI errors
- Run aws logs filter-log-events to extract ERROR messages from the last 30 minutes
- Open Metro and press j/m to use React Native DevTools or the Expo Developer Menu for interactive debugging
FAQ
Read backend package.json scripts (logs:* and logs:watch:*) and extract FUNCTION_NAME from those scripts or from .env.environment files.
Can I capture browser logs automatically during tests?
Yes — use Playwright tools to navigate to the app, collect console messages, check network requests, and run custom JS to inspect client state.
