Menu
Check application logs from local Docker Compose or remote AWS CloudWatch environments. Supports local, staging, and production targets.
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.
Based on SOC occupation classification
| name | ops-check-logs |
| description | Check application logs from local Docker Compose or remote AWS CloudWatch environments. Supports local, staging, and production targets. |
| allowed-tools | ["Bash","Read"] |
Check logs for the Your Project Rails application in the specified environment.
Target environment: $ARGUMENTS (expected: local, staging, or production)
localVerify Docker is running:
docker compose ps
Tail recent logs from web and worker:
docker compose logs --tail=50 web
docker compose logs --tail=50 worker
If the user needs file-based logs, read log/development.log
Summarize any errors, warnings, or notable output
staging or productionSet the AWS profile:
your-project-stagingyour-project-productionCheck AWS session:
aws sts get-caller-identity --profile <profile>
If expired, run: aws sso login --profile <profile>
Discover log groups:
aws logs describe-log-groups \
--profile <profile> \
--region us-east-1 \
--query 'logGroups[].logGroupName' \
--output table
Tail recent logs (last 10 minutes by default):
aws logs tail <log-group> \
--since 10m \
--profile <profile> \
--region us-east-1
Filter for errors if requested:
aws logs filter-log-events \
--log-group-name <log-group> \
--filter-pattern "ERROR" \
--start-time $(date -v-30M +%s000) \
--profile <profile> \
--region us-east-1 \
--query 'events[].message' \
--output text
Summarize findings: error counts, notable patterns, and recommended actions
Check logs now for the specified environment.
Deploy the Your Project Rails application to staging or production. Supports local builds via bin/deploy-staging and CI/CD via branch pushes.
Manage the local Docker Compose development environment. Supports start, stop, restart, and status operations.
Verify that Solid Queue background jobs are running properly. Checks worker health, recurring job execution, and optionally triggers a test job to prove end-to-end processing. Supports local, staging, and production targets.
Verify that OpenTelemetry traces are being collected and exported to X-Ray. Check trace health, find slow requests, investigate errors, and view service dependencies.
Best practices for Rails Action Mailer. Use when writing new mailers, refactoring existing mailers, or when a mailer has inline business logic, missing previews, synchronous delivery, or mixed responsibilities. Applies patterns - single-responsibility mailers, parameterized mailers, deliver_later by default, mailer concerns, service delegation, previews, and structured testing.
Best practices for Rails Active Job with Solid Queue. Use when writing new background jobs, refactoring existing jobs, or when a job has mixed responsibilities, inline business logic, non-idempotent design, or missing error handling. Applies patterns - single-responsibility jobs, argument serialization, idempotent design, retry/discard strategies, queue management, recurring schedules, job concerns, and service delegation.