/dev-logs
View {{DEV_MACHINE}} dev container logs
$ npx -y skills add bybren-llc/safe-agentic-workflow --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/dev-logs
Context preview
What this command does when you run it.
View {{DEV_MACHINE}} dev container logs
Command definition
dev-logs.mddescription: View {{DEV_MACHINE}} dev container logs
argument-hint: [--follow] [--tail N]
allowed-tools: [Read, Write, Edit, Bash, Grep, Glob]> **📋 TEMPLATE**: This command is a template. See "Customization Guide" below to adapt for your infrastructure.
> **DEPRECATED**: This command is an alias to `/remote-logs`. Use `/remote-logs` directly.
This command calls `/remote-logs` which is the canonical command for viewing {{DEV_MACHINE}} container logs.
Usage
/remote-logs
/remote-logs --follow
/remote-logs --tail 500
Why Deprecated?
Per {{TICKET_PREFIX}}-445, we canonicalized around `/remote-*` and `/local-*` naming:
- `/remote-*` = {{DEV_MACHINE}} operations (staging-first, then dev)
- `/local-*` = Local machine operations
Related Commands
- `/remote-logs` - **Canonical** - View {{DEV_MACHINE}} container logs
- `/remote-health` - Health dashboard for {{DEV_MACHINE}}
- `/remote-status` - Check if {{DEV_MACHINE}} needs update
- `/remote-deploy` - Deploy latest image to {{DEV_MACHINE}}
Customization Guide
To adapt this command for your infrastructure, replace these placeholders:
| Placeholder | Description | Example | | ----------------- | ---------------------------- | --------------------------------- | | `{{TICKET_PREFIX}}` | Your Linear ticket prefix | `WOR`, `PROJ`, `TASK` | | `{{DEV_MACHINE}}` | Your remote dev machine name | `Pop OS`, `staging`, `dev-server` |
Read more
description: View {{DEV_MACHINE}} dev container logs
argument-hint: [--follow] [--tail N]
allowed-tools: [Read, Write, Edit, Bash, Grep, Glob]> **📋 TEMPLATE**: This command is a template. See "Customization Guide" below to adapt for your infrastructure.
> **DEPRECATED**: This command is an alias to `/remote-logs`. Use `/remote-logs` directly.
This command calls `/remote-logs` which is the canonical command for viewing {{DEV_MACHINE}} container logs.
Usage
/remote-logs /remote-logs --follow /remote-logs --tail 500
Why Deprecated?
Per {{TICKET_PREFIX}}-445, we canonicalized around `/remote-*` and `/local-*` naming:
- `/remote-*` = {{DEV_MACHINE}} operations (staging-first, then dev)
- `/local-*` = Local machine operations
Related Commands
- `/remote-logs` - **Canonical** - View {{DEV_MACHINE}} container logs
- `/remote-health` - Health dashboard for {{DEV_MACHINE}}
- `/remote-status` - Check if {{DEV_MACHINE}} needs update
- `/remote-deploy` - Deploy latest image to {{DEV_MACHINE}}
Customization Guide
To adapt this command for your infrastructure, replace these placeholders:
| Placeholder | Description | Example | | ----------------- | ---------------------------- | --------------------------------- | | `{{TICKET_PREFIX}}` | Your Linear ticket prefix | `WOR`, `PROJ`, `TASK` | | `{{DEV_MACHINE}}` | Your remote dev machine name | `Pop OS`, `staging`, `dev-server` |
SAW — SAFe Agentic Workflow AI Agent Harness for Multi-Agent Team Workflows Built on SAFe methodology (Scaled Agile Framework), adapted for AI agent teams (Now With AI-DLC!) Works for any team with repeatable processes: Software, Marketing, Research, Legal, Operations.
Other commands on safe-agentic-workflow.
- /audit-deps
Run comprehensive dependency audit
Open command - /check-docker-status
Check if {{DEV_MACHINE}} Docker environment needs updating
Open command - /check-workflow
Quick status check of current workflow state
Open command - /deploy-dev
Deploy latest Docker image to {{DEV_MACHINE}} dev environment
Open command - /dev-health
Check {{DEV_MACHINE}} dev environment health dashboard
Open command - /end-work
Complete work session with final checklist
Open command