codeply-cli 0.5.6 → 0.6.0

package/skills/network-interface-health/SKILL.md

@@ -1,153 +1,153 @@
----
-name: network-interface-health
-description: Diagnose interface errors, drops, CRCs, duplex mismatches, flapping, speed negotiation issues, and counter trends on routers, switches, and Linux hosts.
-metadata:
-  origin: community
----
-
-# Network Interface Health
-
-Use this skill when a network symptom might be caused by a physical link, switch
-port, cable, transceiver, duplex setting, or congested interface.
-
-## When to Use
-
-- A host or VLAN has packet loss, latency spikes, or intermittent reachability.
-- A switch or router interface shows CRCs, runts, giants, drops, resets, or flaps.
-- You need to compare both ends of a link before replacing hardware.
-- A change window needs before/after interface counter evidence.
-- Monitoring reports rising `ifInErrors`, `ifOutErrors`, or `ifOutDiscards`.
-
-## How It Works
-
-Interface counters are evidence, but the trend matters more than the absolute
-number. Capture a baseline, wait a measurement interval, capture again, then
-compare increments.
-
-```text
-show interfaces <interface>
-show interfaces <interface> status
-show logging | include <interface>|changed state|line protocol
-```
-
-On Linux hosts:
-
-```text
-ip -s link show <interface>
-ethtool <interface>
-ethtool -S <interface>
-```
-
-## Counter Reference
-
-| Counter | Meaning | Common cause |
-| --- | --- | --- |
-| CRC | Received frame checksum failed | Bad cable, dirty fiber, bad optic, duplex mismatch |
-| input errors | Aggregate receive-side errors | Check sub-counters before concluding |
-| runts | Frames below minimum Ethernet size | Duplex mismatch, collision domain, faulty NIC |
-| giants | Frames larger than expected MTU | MTU mismatch or jumbo-frame boundary |
-| input drops | Device could not accept inbound packets | Burst, oversubscription, CPU path, queue pressure |
-| output drops | Egress queue discarded packets | Congestion, QoS policy, undersized uplink |
-| resets | Interface hardware reset | Flapping, keepalive, driver, optic, power |
-| collisions | Ethernet collision counter | Half duplex or negotiation mismatch |
-
-## Diagnosis Flow
-
-### CRCs Or Input Errors
-
-1. Confirm counters are incrementing, not just historical.
-2. Check both ends of the link. Receive-side errors usually point to the signal
-   arriving on that side, not necessarily the port reporting the error.
-3. Replace patch cable or clean/replace fiber and optics.
-4. Confirm speed/duplex settings match on both sides.
-5. Check logs for flap events around the same timestamp.
-
-### Drops
-
-1. Separate input drops from output drops.
-2. Compare interface rate against capacity.
-3. Check QoS policy, queue counters, and whether the link is an oversubscribed
-   uplink.
-4. Treat queue tuning as secondary. First prove whether the link is congested.
-
-### Duplex And Speed
-
-Prefer auto-negotiation on modern Ethernet links when both sides support it. If
-one side must be fixed, configure both sides explicitly and document why. Never
-mix fixed speed/duplex on one side with auto on the other.
-
-```text
-show interfaces <interface> | include duplex|speed
-```
-
-## Safe Parser Example
-
-Slice each interface block from one header to the next. Do not use an arbitrary
-character window; large interface blocks can cause counters to be missed or
-assigned to the wrong port.
-
-```python
-import re
-from typing import Any
-
-HEADER_RE = re.compile(
-    r"^(?P<name>\S+) is (?P<status>(?:administratively )?down|up), "
-    r"line protocol is (?P<protocol>up|down)",
-    re.I | re.M,
-)
-ERROR_RE = re.compile(r"(?P<input>\d+) input errors, (?P<crc>\d+) CRC", re.I)
-DROP_RE = re.compile(r"(?P<output>\d+) output errors", re.I)
-DUPLEX_RE = re.compile(r"(?P<duplex>Full|Half|Auto)-duplex,\s+(?P<speed>[^,]+)", re.I)
-
-def parse_show_interfaces(raw: str) -> list[dict[str, Any]]:
-    headers = list(HEADER_RE.finditer(raw))
-    interfaces = []
-    for index, header in enumerate(headers):
-        end = headers[index + 1].start() if index + 1 < len(headers) else len(raw)
-        block = raw[header.start():end]
-        errors = ERROR_RE.search(block)
-        drops = DROP_RE.search(block)
-        duplex = DUPLEX_RE.search(block)
-        interfaces.append({
-            "name": header.group("name"),
-            "status": header.group("status"),
-            "protocol": header.group("protocol"),
-            "duplex": duplex.group("duplex") if duplex else "unknown",
-            "speed": duplex.group("speed").strip() if duplex else "unknown",
-            "input_errors": int(errors.group("input")) if errors else 0,
-            "crc_errors": int(errors.group("crc")) if errors else 0,
-            "output_errors": int(drops.group("output")) if drops else 0,
-        })
-    return interfaces
-```
-
-## Examples
-
-### CRCs On One Switch Port
-
-1. Capture counters on the local port.
-2. Capture counters on the connected remote port.
-3. Replace the cable or optic before changing routing or firewall rules.
-4. Clear counters only after recording the baseline.
-5. Recheck after a fixed interval.
-
-### Internet Slow But LAN Is Fine
-
-1. Check WAN interface drops/errors.
-2. Check LAN uplink utilization and output drops.
-3. Check gateway CPU if the WAN link is clean but throughput is still low.
-4. Compare wired and wireless tests before blaming upstream service.
-
-## Anti-Patterns
-
-- Clearing counters before saving a baseline.
-- Looking at only one side of a link.
-- Assuming all historical CRCs are active problems without a time window.
-- Mixing auto-negotiation on one side with fixed speed/duplex on the other.
-- Treating output drops as a cable problem before checking congestion.
-
-## See Also
-
-- Agent: `network-troubleshooter`
-- Skill: `network-config-validation`
-- Skill: `homelab-network-setup`
+---
+name: network-interface-health
+description: Diagnose interface errors, drops, CRCs, duplex mismatches, flapping, speed negotiation issues, and counter trends on routers, switches, and Linux hosts.
+metadata:
+  origin: community
+---
+
+# Network Interface Health
+
+Use this skill when a network symptom might be caused by a physical link, switch
+port, cable, transceiver, duplex setting, or congested interface.
+
+## When to Use
+
+- A host or VLAN has packet loss, latency spikes, or intermittent reachability.
+- A switch or router interface shows CRCs, runts, giants, drops, resets, or flaps.
+- You need to compare both ends of a link before replacing hardware.
+- A change window needs before/after interface counter evidence.
+- Monitoring reports rising `ifInErrors`, `ifOutErrors`, or `ifOutDiscards`.
+
+## How It Works
+
+Interface counters are evidence, but the trend matters more than the absolute
+number. Capture a baseline, wait a measurement interval, capture again, then
+compare increments.
+
+```text
+show interfaces <interface>
+show interfaces <interface> status
+show logging | include <interface>|changed state|line protocol
+```
+
+On Linux hosts:
+
+```text
+ip -s link show <interface>
+ethtool <interface>
+ethtool -S <interface>
+```
+
+## Counter Reference
+
+| Counter | Meaning | Common cause |
+| --- | --- | --- |
+| CRC | Received frame checksum failed | Bad cable, dirty fiber, bad optic, duplex mismatch |
+| input errors | Aggregate receive-side errors | Check sub-counters before concluding |
+| runts | Frames below minimum Ethernet size | Duplex mismatch, collision domain, faulty NIC |
+| giants | Frames larger than expected MTU | MTU mismatch or jumbo-frame boundary |
+| input drops | Device could not accept inbound packets | Burst, oversubscription, CPU path, queue pressure |
+| output drops | Egress queue discarded packets | Congestion, QoS policy, undersized uplink |
+| resets | Interface hardware reset | Flapping, keepalive, driver, optic, power |
+| collisions | Ethernet collision counter | Half duplex or negotiation mismatch |
+
+## Diagnosis Flow
+
+### CRCs Or Input Errors
+
+1. Confirm counters are incrementing, not just historical.
+2. Check both ends of the link. Receive-side errors usually point to the signal
+   arriving on that side, not necessarily the port reporting the error.
+3. Replace patch cable or clean/replace fiber and optics.
+4. Confirm speed/duplex settings match on both sides.
+5. Check logs for flap events around the same timestamp.
+
+### Drops
+
+1. Separate input drops from output drops.
+2. Compare interface rate against capacity.
+3. Check QoS policy, queue counters, and whether the link is an oversubscribed
+   uplink.
+4. Treat queue tuning as secondary. First prove whether the link is congested.
+
+### Duplex And Speed
+
+Prefer auto-negotiation on modern Ethernet links when both sides support it. If
+one side must be fixed, configure both sides explicitly and document why. Never
+mix fixed speed/duplex on one side with auto on the other.
+
+```text
+show interfaces <interface> | include duplex|speed
+```
+
+## Safe Parser Example
+
+Slice each interface block from one header to the next. Do not use an arbitrary
+character window; large interface blocks can cause counters to be missed or
+assigned to the wrong port.
+
+```python
+import re
+from typing import Any
+
+HEADER_RE = re.compile(
+    r"^(?P<name>\S+) is (?P<status>(?:administratively )?down|up), "
+    r"line protocol is (?P<protocol>up|down)",
+    re.I | re.M,
+)
+ERROR_RE = re.compile(r"(?P<input>\d+) input errors, (?P<crc>\d+) CRC", re.I)
+DROP_RE = re.compile(r"(?P<output>\d+) output errors", re.I)
+DUPLEX_RE = re.compile(r"(?P<duplex>Full|Half|Auto)-duplex,\s+(?P<speed>[^,]+)", re.I)
+
+def parse_show_interfaces(raw: str) -> list[dict[str, Any]]:
+    headers = list(HEADER_RE.finditer(raw))
+    interfaces = []
+    for index, header in enumerate(headers):
+        end = headers[index + 1].start() if index + 1 < len(headers) else len(raw)
+        block = raw[header.start():end]
+        errors = ERROR_RE.search(block)
+        drops = DROP_RE.search(block)
+        duplex = DUPLEX_RE.search(block)
+        interfaces.append({
+            "name": header.group("name"),
+            "status": header.group("status"),
+            "protocol": header.group("protocol"),
+            "duplex": duplex.group("duplex") if duplex else "unknown",
+            "speed": duplex.group("speed").strip() if duplex else "unknown",
+            "input_errors": int(errors.group("input")) if errors else 0,
+            "crc_errors": int(errors.group("crc")) if errors else 0,
+            "output_errors": int(drops.group("output")) if drops else 0,
+        })
+    return interfaces
+```
+
+## Examples
+
+### CRCs On One Switch Port
+
+1. Capture counters on the local port.
+2. Capture counters on the connected remote port.
+3. Replace the cable or optic before changing routing or firewall rules.
+4. Clear counters only after recording the baseline.
+5. Recheck after a fixed interval.
+
+### Internet Slow But LAN Is Fine
+
+1. Check WAN interface drops/errors.
+2. Check LAN uplink utilization and output drops.
+3. Check gateway CPU if the WAN link is clean but throughput is still low.
+4. Compare wired and wireless tests before blaming upstream service.
+
+## Anti-Patterns
+
+- Clearing counters before saving a baseline.
+- Looking at only one side of a link.
+- Assuming all historical CRCs are active problems without a time window.
+- Mixing auto-negotiation on one side with fixed speed/duplex on the other.
+- Treating output drops as a cable problem before checking congestion.
+
+## See Also
+
+- Agent: `network-troubleshooter`
+- Skill: `network-config-validation`
+- Skill: `homelab-network-setup`

package/skills/nextjs-turbopack/SKILL.md

@@ -1,58 +1,58 @@
----
-name: nextjs-turbopack
-description: Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.
-metadata:
-  origin: ECC
----
-
-# Next.js and Turbopack
-
-Next.js 16+ uses Turbopack by default for local development: an incremental bundler written in Rust that significantly speeds up dev startup and hot updates.
-
-## When to Use
-
-- **Turbopack (default dev)**: Use for day-to-day development. Faster cold start and HMR, especially in large apps.
-- **Webpack (legacy dev)**: Use only if you hit a Turbopack bug or rely on a webpack-only plugin in dev. Disable with `--webpack` (or `--no-turbopack` depending on your Next.js version; check the docs for your release).
-- **Production**: Production build behavior (`next build`) may use Turbopack or webpack depending on Next.js version; check the official Next.js docs for your version.
-
-Use when: developing or debugging Next.js 16+ apps, diagnosing slow dev startup or HMR, or optimizing production bundles.
-
-## How It Works
-
-- **Turbopack**: Incremental bundler for Next.js dev. Uses file-system caching so restarts are much faster (e.g. 5–14x on large projects).
-- **Default in dev**: From Next.js 16, `next dev` runs with Turbopack unless disabled.
-- **File-system caching**: Restarts reuse previous work; cache is typically under `.next`; no extra config needed for basic use.
-- **Bundle Analyzer (Next.js 16.1+)**: Experimental Bundle Analyzer to inspect output and find heavy dependencies; enable via config or experimental flag (see Next.js docs for your version).
-
-## Examples
-
-### Commands
-
-```bash
-next dev
-next build
-next start
-```
-
-### Usage
-
-Run `next dev` for local development with Turbopack. Use the Bundle Analyzer (see Next.js docs) to optimize code-splitting and trim large dependencies. Prefer App Router and server components where possible.
-
-## Middleware File Naming
-
-Next.js 16 introduced `proxy.ts` as the middleware filename, replacing the older `middleware.ts` convention:
-
-- **Next.js 16+**: use `proxy.ts` at the project root
-- **Pre-Next.js 16**: use `middleware.ts` at the project root
-
-The filename change is tied to the **Next.js version**, not to which bundler (Turbopack or webpack) is in use. Always check the official docs for the version you are reviewing.
-
-**Do not flag `proxy.ts` as a misnamed or missing middleware file in Next.js 16 projects.** The file is correct and intentional. Suggesting a rename to `middleware.ts` will break middleware execution.
-
-Reference: [Next.js proxy docs](https://nextjs.org/docs/app/getting-started/proxy)
-
-## Best Practices
-
-- Stay on a recent Next.js 16.x for stable Turbopack and caching behavior.
-- If dev is slow, ensure you're on Turbopack (default) and that the cache isn't being cleared unnecessarily.
-- For production bundle size issues, use the official Next.js bundle analysis tooling for your version.
+---
+name: nextjs-turbopack
+description: Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.
+metadata:
+  origin: ECC
+---
+
+# Next.js and Turbopack
+
+Next.js 16+ uses Turbopack by default for local development: an incremental bundler written in Rust that significantly speeds up dev startup and hot updates.
+
+## When to Use
+
+- **Turbopack (default dev)**: Use for day-to-day development. Faster cold start and HMR, especially in large apps.
+- **Webpack (legacy dev)**: Use only if you hit a Turbopack bug or rely on a webpack-only plugin in dev. Disable with `--webpack` (or `--no-turbopack` depending on your Next.js version; check the docs for your release).
+- **Production**: Production build behavior (`next build`) may use Turbopack or webpack depending on Next.js version; check the official Next.js docs for your version.
+
+Use when: developing or debugging Next.js 16+ apps, diagnosing slow dev startup or HMR, or optimizing production bundles.
+
+## How It Works
+
+- **Turbopack**: Incremental bundler for Next.js dev. Uses file-system caching so restarts are much faster (e.g. 5–14x on large projects).
+- **Default in dev**: From Next.js 16, `next dev` runs with Turbopack unless disabled.
+- **File-system caching**: Restarts reuse previous work; cache is typically under `.next`; no extra config needed for basic use.
+- **Bundle Analyzer (Next.js 16.1+)**: Experimental Bundle Analyzer to inspect output and find heavy dependencies; enable via config or experimental flag (see Next.js docs for your version).
+
+## Examples
+
+### Commands
+
+```bash
+next dev
+next build
+next start
+```
+
+### Usage
+
+Run `next dev` for local development with Turbopack. Use the Bundle Analyzer (see Next.js docs) to optimize code-splitting and trim large dependencies. Prefer App Router and server components where possible.
+
+## Middleware File Naming
+
+Next.js 16 introduced `proxy.ts` as the middleware filename, replacing the older `middleware.ts` convention:
+
+- **Next.js 16+**: use `proxy.ts` at the project root
+- **Pre-Next.js 16**: use `middleware.ts` at the project root
+
+The filename change is tied to the **Next.js version**, not to which bundler (Turbopack or webpack) is in use. Always check the official docs for the version you are reviewing.
+
+**Do not flag `proxy.ts` as a misnamed or missing middleware file in Next.js 16 projects.** The file is correct and intentional. Suggesting a rename to `middleware.ts` will break middleware execution.
+
+Reference: [Next.js proxy docs](https://nextjs.org/docs/app/getting-started/proxy)
+
+## Best Practices
+
+- Stay on a recent Next.js 16.x for stable Turbopack and caching behavior.
+- If dev is slow, ensure you're on Turbopack (default) and that the cache isn't being cleared unnecessarily.
+- For production bundle size issues, use the official Next.js bundle analysis tooling for your version.

package/skills/nodejs-keccak256/SKILL.md

@@ -1,103 +1,103 @@
----
-name: nodejs-keccak256
-description: Prevent Ethereum hashing bugs in JavaScript and TypeScript. Node's sha3-256 is NIST SHA3, not Ethereum Keccak-256, and silently breaks selectors, signatures, storage slots, and address derivation.
-metadata:
-  origin: ECC direct-port adaptation
-version: "1.0.0"
----
-
-# Node.js Keccak-256
-
-Ethereum uses Keccak-256, not the NIST-standardized SHA3 variant exposed by Node's `crypto.createHash('sha3-256')`.
-
-## When to Use
-
-- Computing Ethereum function selectors or event topics
-- Building EIP-712, signature, Merkle, or storage-slot helpers in JS/TS
-- Reviewing any code that hashes Ethereum data with Node crypto directly
-
-## How It Works
-
-The two algorithms produce different outputs for the same input, and Node will not warn you.
-
-```javascript
-import crypto from 'crypto';
-import { keccak256, toUtf8Bytes } from 'ethers';
-
-const data = 'hello';
-const nistSha3 = crypto.createHash('sha3-256').update(data).digest('hex');
-const keccak = keccak256(toUtf8Bytes(data)).slice(2);
-
-console.log(nistSha3 === keccak); // false
-```
-
-## Examples
-
-### ethers v6
-
-```typescript
-import { keccak256, toUtf8Bytes, solidityPackedKeccak256, id } from 'ethers';
-
-const hash = keccak256(new Uint8Array([0x01, 0x02]));
-const hash2 = keccak256(toUtf8Bytes('hello'));
-const topic = id('Transfer(address,address,uint256)');
-const packed = solidityPackedKeccak256(
-  ['address', 'uint256'],
-  ['0x742d35Cc6634C0532925a3b8D4C9B569890FaC1c', 100n],
-);
-```
-
-### viem
-
-```typescript
-import { keccak256, toBytes } from 'viem';
-
-const hash = keccak256(toBytes('hello'));
-```
-
-### web3.js
-
-```javascript
-const hash = web3.utils.keccak256('hello');
-const packed = web3.utils.soliditySha3(
-  { type: 'address', value: '0x742d35Cc6634C0532925a3b8D4C9B569890FaC1c' },
-  { type: 'uint256', value: '100' },
-);
-```
-
-### Common patterns
-
-```typescript
-import { id, keccak256, AbiCoder } from 'ethers';
-
-const selector = id('transfer(address,uint256)').slice(0, 10);
-const typeHash = keccak256(toUtf8Bytes('Transfer(address from,address to,uint256 value)'));
-
-function getMappingSlot(key: string, mappingSlot: number): string {
-  return keccak256(
-    AbiCoder.defaultAbiCoder().encode(['address', 'uint256'], [key, mappingSlot]),
-  );
-}
-```
-
-### Address from public key
-
-```typescript
-import { keccak256 } from 'ethers';
-
-function pubkeyToAddress(pubkeyBytes: Uint8Array): string {
-  const hash = keccak256(pubkeyBytes.slice(1));
-  return '0x' + hash.slice(-40);
-}
-```
-
-### Audit your codebase
-
-```bash
-grep -rn "createHash.*sha3" --include="*.ts" --include="*.js" --exclude-dir=node_modules .
-grep -rn "keccak256" --include="*.ts" --include="*.js" . | grep -v node_modules
-```
-
-## Rule
-
-For Ethereum contexts, never use `crypto.createHash('sha3-256')`. Use Keccak-aware helpers from `ethers`, `viem`, `web3`, or another explicit Keccak implementation.
+---
+name: nodejs-keccak256
+description: Prevent Ethereum hashing bugs in JavaScript and TypeScript. Node's sha3-256 is NIST SHA3, not Ethereum Keccak-256, and silently breaks selectors, signatures, storage slots, and address derivation.
+metadata:
+  origin: ECC direct-port adaptation
+version: "1.0.0"
+---
+
+# Node.js Keccak-256
+
+Ethereum uses Keccak-256, not the NIST-standardized SHA3 variant exposed by Node's `crypto.createHash('sha3-256')`.
+
+## When to Use
+
+- Computing Ethereum function selectors or event topics
+- Building EIP-712, signature, Merkle, or storage-slot helpers in JS/TS
+- Reviewing any code that hashes Ethereum data with Node crypto directly
+
+## How It Works
+
+The two algorithms produce different outputs for the same input, and Node will not warn you.
+
+```javascript
+import crypto from 'crypto';
+import { keccak256, toUtf8Bytes } from 'ethers';
+
+const data = 'hello';
+const nistSha3 = crypto.createHash('sha3-256').update(data).digest('hex');
+const keccak = keccak256(toUtf8Bytes(data)).slice(2);
+
+console.log(nistSha3 === keccak); // false
+```
+
+## Examples
+
+### ethers v6
+
+```typescript
+import { keccak256, toUtf8Bytes, solidityPackedKeccak256, id } from 'ethers';
+
+const hash = keccak256(new Uint8Array([0x01, 0x02]));
+const hash2 = keccak256(toUtf8Bytes('hello'));
+const topic = id('Transfer(address,address,uint256)');
+const packed = solidityPackedKeccak256(
+  ['address', 'uint256'],
+  ['0x742d35Cc6634C0532925a3b8D4C9B569890FaC1c', 100n],
+);
+```
+
+### viem
+
+```typescript
+import { keccak256, toBytes } from 'viem';
+
+const hash = keccak256(toBytes('hello'));
+```
+
+### web3.js
+
+```javascript
+const hash = web3.utils.keccak256('hello');
+const packed = web3.utils.soliditySha3(
+  { type: 'address', value: '0x742d35Cc6634C0532925a3b8D4C9B569890FaC1c' },
+  { type: 'uint256', value: '100' },
+);
+```
+
+### Common patterns
+
+```typescript
+import { id, keccak256, AbiCoder } from 'ethers';
+
+const selector = id('transfer(address,uint256)').slice(0, 10);
+const typeHash = keccak256(toUtf8Bytes('Transfer(address from,address to,uint256 value)'));
+
+function getMappingSlot(key: string, mappingSlot: number): string {
+  return keccak256(
+    AbiCoder.defaultAbiCoder().encode(['address', 'uint256'], [key, mappingSlot]),
+  );
+}
+```
+
+### Address from public key
+
+```typescript
+import { keccak256 } from 'ethers';
+
+function pubkeyToAddress(pubkeyBytes: Uint8Array): string {
+  const hash = keccak256(pubkeyBytes.slice(1));
+  return '0x' + hash.slice(-40);
+}
+```
+
+### Audit your codebase
+
+```bash
+grep -rn "createHash.*sha3" --include="*.ts" --include="*.js" --exclude-dir=node_modules .
+grep -rn "keccak256" --include="*.ts" --include="*.js" . | grep -v node_modules
+```
+
+## Rule
+
+For Ethereum contexts, never use `crypto.createHash('sha3-256')`. Use Keccak-aware helpers from `ethers`, `viem`, `web3`, or another explicit Keccak implementation.