iproute-debug

Diagnose iproute2 bugs in JSON output, argument parsing, kernel compatibility, and memory handling.

Updated Nov 29, 2025
One-click install
npx skills add https://github.com/thimslugga/agent-skills --skill iproute-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iproute-debug
Source: https://github.com/thimslugga/agent-skills/tree/main/skills/linux/linux-review/iproute-debug
Command: npx skills add https://github.com/thimslugga/agent-skills --skill iproute-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Debug iproute2 issues including JSON output problems, argument parsing bugs, kernel compatibility failures, and memory issues within iproute2 source trees.

Core Features & Use Cases

  • Load relevant context files (references/json-output.md, references/argument-parsing.md, references/kernel-compat.md, references/common-bugs.md) to frame the issue.
  • Analyze the problem description, search code paths, identify root causes, and propose fixes.
  • Use when troubleshooting ip, tc, bridge, or other iproute2 utilities in the Linux networking stack.

Quick Start

Load the relevant context files and describe a fix for the described iproute2 issue.

Frequently Asked Questions about iproute-debug

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

FAQPage Schema
How do I debug iproute2 JSON output problems and argument parsing bugs?

Debug iproute2 JSON output problems and argument parsing bugs by loading relevant context references to frame the issue, analyzing code paths within the iproute2 source tree, identifying root causes, and proposing concrete fixes for the affected utilities.

Why does iproute2 fail with kernel compatibility issues when using ip or tc commands?

Kernel compatibility failures in iproute2 commands like ip and tc can be diagnosed by analyzing the problem description against kernel compatibility references, locating code path mismatches, and suggesting modifications to resolve the interface failures.

What is the best way to troubleshoot memory management issues in the Linux networking stack?

Troubleshooting memory management issues in the Linux networking stack involves analyzing iproute2 source trees, searching code paths for memory handling bugs, identifying root causes, and proposing concrete modifications to fix the memory leaks or faults.

Can I use this approach to fix bridge utility bugs within the iproute2 source tree?

Yes, you can fix bridge utility bugs within the iproute2 source tree by loading relevant context files, analyzing the problem description, searching code paths, identifying root causes, and proposing concrete modifications to resolve the issue.

Does iproute2 debugging work for JSON output, CLI parsing, kernel compatibility, and memory handling simultaneously?

Yes, iproute2 debugging works across JSON output, CLI argument parsing, kernel compatibility, and memory handling simultaneously by loading relevant context references to frame each specific issue and proposing targeted fixes for the diagnosed bugs.

What should I do when iproute2 debugging does not locate the root cause of a tc command bug?

When iproute2 debugging does not locate the root cause of a tc command bug, ensure all relevant context files are loaded to frame the issue properly, then re-analyze the problem description and search code paths to identify the missed root cause.