'Stream Devvit logs for an installed app (trigger phrases: "devvit logs", "stream logs", "check logs", "show logs"). Requires the user to provide the target subreddit.'
Devvit Logs
Stream log events from an installed Devvit app for quick debugging. This skill wraps devvit logs and auto-exits after a short window (5 seconds) to avoid hanging on a streaming command.
How It Works
- Ask the user for the target subreddit (required).
- Optionally accept an app name and
--since=...flag. - Run
devvit logsand capture output. - Exit automatically after the first burst of output or 5 seconds, whichever comes first.
Usage
node /mnt/skills/user/devvit-logs/scripts/devvit-logs.js <subreddit> [app-name] [--since=1h]
Arguments:
subreddit- Required. Subreddit to stream logs from.app-name- Optional. App name if streaming from another folder.--since=Xd- Optional. Historical logs window (e.g.,--since=30m,--since=1d).
Examples:
node /mnt/skills/user/devvit-logs/scripts/devvit-logs.js my-subreddit
node /mnt/skills/user/devvit-logs/scripts/devvit-logs.js my-subreddit my-app --since=1h
Output
{
"ok": true,
"reason": "timeout",
"exitCode": null,
"signal": null,
"stdout": "=============================== streaming logs for my-app on my-subreddit ================================\n[DEBUG] Dec 8 15:55:23 Action called!",
"stderr": ""
}
Present Results to User
- If the user did not provide a subreddit, ask for it explicitly.
- Summarize the captured logs (if any) and mention the 5-second capture window.
- If no logs were captured, say so and suggest retrying with activity or
--since=....
Troubleshooting
- Devvit CLI not found: Install or ensure
devvitis in PATH. - Not logged in: Run
devvit loginand try again. - No logs: Trigger an action in the app or use
--since=.... - Permission errors: Confirm the app is installed in the subreddit and you have access.
You Might Also Like
Related Skills

fix
Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.
facebook
frontend-testing
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
langgenius
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews while applying the checklist rules.
langgenius
code-reviewer
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
google-gemini
session-logs
Search and analyze your own session logs (older/parent conversations) using jq.
moltbot

