skills.rest
airhorns
airhornsCOMMUNITY
Explore all skills by this author →
Website𝕏@harrybrundageGitHub

jam-runtime-logs

Capture and manage logs from long-running Jam dev servers.

Updated Mar 22, 2026
Search Tags:#monitoring#logs#logging#process-management#dev-ops#tail#background-task
One-click install
npx skills add https://github.com/airhorns/jam --skill jam-runtime-logs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jam-runtime-logs
Source: https://github.com/airhorns/jam/tree/main/.agents/skills/jam-runtime-logs
Command: npx skills add https://github.com/airhorns/jam --skill jam-runtime-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Always preserve logs for long-running Jam dev servers and backend-like processes so failures can be diagnosed after the fact. Use the scratch/ directory to store these logs and share them with teammates.

Core Features & Use Cases

  • Foreground log capture: start a process and stream logs into scratch/logs for immediate visibility.
  • Background process management: run services detached from the terminal with log retention for later analysis.
  • Inspect, stop, and verify: quickly view recent log output and terminate processes by PID when needed.
  • Port-awareness: detect port conflicts and identify the owning process before retrying.
  • Handoff readiness: record paths and relevant error lines in workpads or PR notes for sharing context.

Quick Start

Start a long-running Jam process and automatically capture its logs to scratch/logs for later inspection.

Frequently Asked Questions about jam-runtime-logs

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

FAQPage Schema
How do I preserve logs from a long-running dev server for later debugging?▼

You can capture long-running process output into a scratch/logs directory using simple foreground and background capture commands. This retains dev server logs for post-failure diagnosis and teammate handoff.

How do I run a background process and keep the logs for later analysis?▼

Running a background process with log retention involves detaching the service from the terminal while routing its output to stored log files. You can then inspect recent output and terminate the process by its PID when needed.

How do I detect port conflicts when starting a long-running process?▼

Detecting port conflicts is handled through built-in port-awareness that identifies the owning process before retrying. This allows you to manage port conflicts and terminate the blocking process by PID before starting your dev server.

Do I need a specific directory setup to capture and store process logs?▼

Yes, you need a scratch/logs directory to store captured logs from long-running processes. This dedicated storage location is required to reliably save output for debugging workflows and share context with teammates.

What is the best way to share long-running process logs with teammates for debugging?▼

The best way to share logs for debugging is to store them in a scratch directory and record the file paths alongside relevant error lines in workpads or PR notes. This ensures full context is available for teammate handoff.

Related Skills

Explore More Software Engineering Skills→
imehrimehr

local-dev-workflow

Generates start.sh scripts with port conflict management and dashboard output.

Community
Advanced
INNERJOINTINNERJOINT

learner

Extract conversation insights into structured Expertise and Workflow documents.

Community
Advanced
joserprietojoserprieto
2

service-manager

Orchestrate background services with PID tracking, health checks, and log rotation.

Community
Advanced
BagelHoleBagelHole
46

audit-logging

Implement centralized audit logging with Fluentd and Elasticsearch.

Community
Intermediate