Skip to content

Add debugging skills and repo-specific patterns for container services - #329

Merged
bubacoder merged 1 commit into
mainfrom
debug-container-service
Jun 5, 2026
Merged

Add debugging skills and repo-specific patterns for container services#329
bubacoder merged 1 commit into
mainfrom
debug-container-service

Conversation

@bubacoder

@bubacoder bubacoder commented May 18, 2026

Copy link
Copy Markdown
Owner

Summary by CodeRabbit

  • Documentation
    • Added comprehensive troubleshooting guide for debugging container-based services, including systematic workflows for log analysis, configuration verification, issue investigation, and resolution strategies.

@coderabbitai

coderabbitai Bot commented May 18, 2026

Copy link
Copy Markdown
Contributor

Looking for one thing? Review this PR in Change Stack to search files, summaries, diffs, and code without losing your place.

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8c5eb013-5804-4f78-bad2-72fb76292842

📥 Commits

Reviewing files that changed from the base of the PR and between 8430072 and ff21321.

📒 Files selected for processing (1)
  • .claude/skills/debug-container-service/SKILL.md

Walkthrough

Adds a comprehensive debugging skill document for container service troubleshooting in the homelab infrastructure. The skill defines a seven-step workflow: fetching resolved Docker Compose configuration, reading container logs, checking mounted volume logs, searching documentation, triaging GitHub issues, analyzing release notes, and performing last-resort source inspection and patching with explicit confirmation.

Changes

Container Service Debugging Skill

Layer / File(s) Summary
Skill metadata and workflow framing
.claude/skills/debug-container-service/SKILL.md
Skill document front-matter defines the "Container Service Debugging" workflow with the stop-when-resolved rule and required inputs (symptom/error and service category/name).
Core troubleshooting steps 1–6
.claude/skills/debug-container-service/SKILL.md
Six-step investigative procedure: (1) fetch resolved compose config via MCP and extract container name, volumes, environment variables, and image tag; (2) read Docker logs with filtering options; (3) derive and search file-based logs in mounted volumes; (4) search documentation and source code for exact environment/config names; (5) search GitHub issues using error keywords; (6) list container tags, read release notes, and decide between upgrade and downgrade paths.
Last-resort source inspection and patching (Step 7)
.claude/skills/debug-container-service/SKILL.md
Advanced Step 7 procedure for when earlier steps fail: requires agent to explain and obtain confirmation for intended changes, read deployed source, enumerate fix options ranked by invasiveness (environment/config, patched bind-mount, custom image), require reverting wrong fixes, and mandate container recreation and log re-verification.

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding a debugging skill document for container services with troubleshooting workflows.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch debug-container-service

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.claude/skills/debug-container-service/references/repo-specifics.md:
- Around line 22-24: The two fenced code blocks containing the path
"/mnt/local/storage/docker-volumes/<service-name>/" and the command
"mcp__infra-mcp__container-service-recreate(service_name=\"category/service-name\")"
are missing language identifiers; add a language tag (e.g., ```text) to each
opening fence so they become "```text" to satisfy markdownlint MD040 and ensure
both blocks (the one with /mnt/local/storage/docker-volumes/<service-name>/ and
the one with mcp__infra-mcp__container-service-recreate(...)) are updated.
- Line 13: Update the documentation line that describes Docker Compose container
naming: replace the legacy pattern reference `<project>_<service>` with the
current Docker Compose v2 default pattern `<project>-<service>-1` and mention
that this hyphenated format is used when `container_name:` is not set so users
see the correct, DNS-safe naming behavior.

In @.claude/skills/debug-container-service/SKILL.md:
- Around line 30-32: Update the fenced code blocks in
.claude/skills/debug-container-service/SKILL.md to include an explicit language
tag (e.g., use ```text or ```bash) so markdownlint MD040 is satisfied;
specifically add the language tag to the block containing
mcp__infra-mcp__container-service-config(service_name="category/service-name")
and to the block with mcp__context7__resolve-library-id(...) and
mcp__context7__query-docs(...), and apply the same change to the other similar
fence around the same snippets referenced in the comment.
- Around line 73-78: The example commands in Step 3 hardcode the volume root
(/mnt/local/storage/docker-volumes/...), which contradicts the earlier
instruction to use the compose-derived DOCKER_VOLUMES path; update the two find
examples to use the variable placeholder (e.g. ${DOCKER_VOLUMES}/<service>/) or
reference the compose-derived path instead of the literal path so the examples
align with the compose config guidance in Step 1 and work on hosts with
different volume roots.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 61443a85-d63c-4b40-a9ea-1629e4cc0277

📥 Commits

Reviewing files that changed from the base of the PR and between 46ec6ce and 8430072.

📒 Files selected for processing (2)
  • .claude/skills/debug-container-service/SKILL.md
  • .claude/skills/debug-container-service/references/repo-specifics.md

Comment thread .claude/skills/debug-container-service/references/repo-specifics.md Outdated
Comment thread .claude/skills/debug-container-service/references/repo-specifics.md Outdated
Comment thread .claude/skills/debug-container-service/SKILL.md
Comment thread .claude/skills/debug-container-service/SKILL.md Outdated
@bubacoder
bubacoder force-pushed the debug-container-service branch from 8430072 to ff21321 Compare June 5, 2026 19:25
@bubacoder
bubacoder merged commit 2354ede into main Jun 5, 2026
4 checks passed
@bubacoder
bubacoder deleted the debug-container-service branch June 5, 2026 19:45
This was referenced Jun 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant