fetch-deployment-logs

Fetch and filter deployment logs from a Repl to debug production errors.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/gopaljilab/Gupta-Portfolio --skill fetch-deployment-logs-gopaljilab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fetch-deployment-logs
Source: https://github.com/gopaljilab/Gupta-Portfolio/tree/main/.local/skills/fetch-deployment-logs
Command: npx skills add https://github.com/gopaljilab/Gupta-Portfolio --skill fetch-deployment-logs-gopaljilab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a deployed application misbehaves, developers often lack visibility into what is happening in production. This Skill retrieves deployment logs from the current Repl so you can diagnose runtime errors, startup failures, and unexpected behavior without leaving your workspace. ## Core Features & Use Cases - Time-Range Filtering: Fetch logs after or before specific Unix timestamps to focus on the window when an issue occurred. - Regex Message Filtering: Use RE2 regular expressions to isolate errors, warnings, database issues, or any pattern in log messages. - Context Lines: Retrieve surrounding lines before and after each match, similar to grep -C, to understand the full error context. - Use Case: A user reports their deployed site returns errors. You fetch logs from the last hour filtered by "ERROR" with 10 lines of context, identify a database connection failure, and pinpoint the root cause. ## Quick Start Ask the assistant to fetch deployment logs from the last hour and show any errors to debug why the deployed app is failing.

Frequently Asked Questions about fetch-deployment-logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check deployment logs for my Repl app?▼

Call the fetchDeploymentLogs function in the JavaScript notebook with no arguments to retrieve all available logs, or pass an afterTimestamp to limit results to a recent time window. The result contains a logs string and a found boolean.

How to filter deployment logs for errors only?▼

Pass a message parameter with a regex pattern like "ERROR" or "(?i)(error|exception|failed)" to fetchDeploymentLogs. The filter uses RE2 syntax, so case-insensitive matching works with the (?i) prefix.

Can I see log lines around a specific error match?▼

Yes, use the messageContext parameter with lines (0-100) and limit (1-10) values. This returns surrounding lines before and after each regex match, similar to grep -C, which helps understand the error context.

Why does fetching deployment logs return no results?▼

No results usually means the deployment has not run recently or no logs match your filter criteria. Try removing the message regex, widening the timestamp range, or verifying the application was actually deployed and generating logs.

What regex patterns find database connection errors in logs?▼

Use a pattern like "(?i)(database|postgres|mysql|mongo|connection.*refused)" as the message parameter. This matches common database-related log entries including connection refusals across different database systems.