Docker Cli Skills

1. Check if it exists but is stopped: docker ps -a --filter "name=dev-cli-tools"
2. Start it if stopped: docker start dev-cli-tools
3. If it doesn't exist, inform the user and suggest creating it

Command Execution Pattern

Base pattern for all CLI commands:

docker exec dev-cli-tools <command> <arguments>

Interactive commands (if needed):

docker exec -it dev-cli-tools <command> <arguments>

Jira Commands via Container

Instead of running jira directly, wrap it with docker exec:

Nested command substitution:

When a command uses command substitution like $(jira me), wrap the inner command too:

# Instead of: jira issue list -a$(jira me)
docker exec dev-cli-tools sh -c 'jira issue list -a$(jira me)'

Or run the inner command separately first:

$user = docker exec dev-cli-tools jira me
docker exec dev-cli-tools jira issue list -a$user

Confluence Commands via Container

Instead of running confluence directly, wrap it with docker exec:

Multi-line Commands and Complex Input

For commands with multi-line input or complex quoting:

# Option 1: Use here-strings (PowerShell)
$content = @"
Multi-line content here
Can span multiple lines
"@
docker exec dev-cli-tools confluence page create --space KEY --title "Title" --body $content

# Option 2: Write to a temp file in container
docker exec dev-cli-tools sh -c "echo 'content' > /tmp/input.txt"
docker exec dev-cli-tools jira issue create -tTask -s"Summary" -b"$(cat /tmp/input.txt)"

Environment Variables

Pass environment variables to container commands:

docker exec -e JIRA_API_TOKEN=$env:JIRA_API_TOKEN dev-cli-tools jira me

Or use variables already set in the container (preferred if configured):

# Variables should be configured when starting the container
docker exec dev-cli-tools jira me

File Operations

If CLI tools need to access files:

1. Copy files into container:

   docker cp local-file.txt dev-cli-tools:/tmp/
   docker exec dev-cli-tools confluence page create --space KEY --body-file /tmp/local-file.txt
   

2. Copy output from container:

   docker exec dev-cli-tools confluence page view 12345 --output json > output.json
   

3. Use mounted volumes (if container was started with volume mounts):

   # Assuming /workspace is mounted in container
   docker exec dev-cli-tools jira issue create -tTask -s"Summary" -b"$(cat /workspace/description.txt)"
   

Error Handling

Container not found:

Error: No such container: dev-cli-tools
→ Inform user to start or create the container

Command not found in container:

Error: executable file not found in $PATH
→ The CLI tool may not be installed in the container
→ Check with: docker exec dev-cli-tools which jira

Permission denied:

→ May need to run with different user: docker exec -u root dev-cli-tools <command>

Troubleshooting

Check what's installed in the container:

docker exec dev-cli-tools which jira
docker exec dev-cli-tools which confluence
docker exec dev-cli-tools ls /usr/local/bin

Verify container configuration:

docker inspect dev-cli-tools

Check container logs:

docker logs dev-cli-tools

Examples

Complete workflow for viewing a Jira issue:

# 1. Check container is running
docker ps --filter "name=dev-cli-tools" --filter "status=running"

# 2. Execute the command
docker exec dev-cli-tools jira issue view PROJ-123

Complete workflow for searching Confluence:

# 1. Check container is running
docker ps --filter "name=dev-cli-tools" --filter "status=running"

# 2. Execute search
docker exec dev-cli-tools confluence page search "deployment guide"

# 3. View specific page from results
docker exec dev-cli-tools confluence page view 12345

Integration with Other Skills

When the jira or confluence skills are loaded:

1. First load this docker-cli-skills skill
2. Apply the docker exec dev-cli-tools wrapper to all CLI commands
3. Follow the normal workflow from those skills, but with containerized execution

Priority: This skill takes precedence over direct CLI execution in jira/confluence skills.