codeply-cli 0.5.1 → 0.5.2

package/skills/cisco-ios-patterns/SKILL.md

@@ -1,164 +1,164 @@
----
-name: cisco-ios-patterns
-description: Cisco IOS and IOS-XE review patterns for show commands, config hierarchy, wildcard masks, ACL placement, interface hygiene, and safe change-window verification.
-metadata:
-  origin: community
----
-
-# Cisco IOS Patterns
-
-Use this skill when reviewing Cisco IOS or IOS-XE snippets, building a
-change-window checklist, or explaining how to collect evidence from a router or
-switch without making the incident worse.
-
-## When to Use
-
-- Reviewing IOS or IOS-XE configuration before a planned change.
-- Choosing read-only `show` commands for troubleshooting.
-- Checking ACL wildcard masks and interface direction.
-- Explaining global, interface, routing process, and line configuration modes.
-- Verifying that a change landed in running config and was saved intentionally.
-
-## Operating Rules
-
-Treat IOS examples as patterns, not paste-ready production changes. Confirm the
-platform, interface names, current config, rollback path, and out-of-band access
-before making changes on a real device.
-
-Prefer this workflow:
-
-1. Capture current state with read-only commands.
-2. Review the exact candidate config.
-3. Confirm management access cannot be locked out.
-4. Apply the smallest change in a maintenance window.
-5. Re-read state, compare to the baseline, then save only after validation.
-
-## Mode Reference
-
-```text
-Router> enable
-Router# show running-config
-Router# configure terminal
-Router(config)# interface GigabitEthernet0/1
-Router(config-if)# description UPLINK-TO-CORE
-Router(config-if)# no shutdown
-Router(config-if)# exit
-Router(config)# end
-Router# show running-config interface GigabitEthernet0/1
-```
-
-`running-config` is active memory. `startup-config` is what survives reload.
-Do not save a change just because a command was accepted; validate behavior
-first, then use `copy running-config startup-config` if the change is approved.
-
-## Read-Only Collection
-
-```text
-show version
-show inventory
-show processes cpu sorted
-show memory statistics
-show logging
-show running-config | section line vty
-show running-config | section interface
-show running-config | section router bgp
-show ip interface brief
-show interfaces
-show interfaces status
-show vlan brief
-show mac address-table
-show spanning-tree
-show ip route
-show ip protocols
-show ip access-lists
-show route-map
-show ip prefix-list
-```
-
-Collect the specific section you need instead of dumping full config into a
-ticket when the config may contain secrets, customer names, or private topology.
-
-## Wildcard Masks
-
-IOS ACL and many routing statements use wildcard masks, not subnet masks.
-
-```text
-Subnet mask       Wildcard mask
-255.255.255.255   0.0.0.0
-255.255.255.252   0.0.0.3
-255.255.255.0     0.0.0.255
-255.255.0.0       0.0.255.255
-```
-
-Review wildcard masks before deployment. A subnet mask accidentally used as a
-wildcard can match far more traffic than intended.
-
-```text
-ip access-list extended WEB-IN
-  10 permit tcp 192.0.2.0 0.0.0.255 any eq 443
-  999 deny ip any any log
-```
-
-Every ACL has an implicit deny at the end. Add an explicit logged deny when the
-operational goal includes observing misses, and confirm logging volume is safe.
-
-## ACL Placement Review
-
-Before applying an ACL to an interface, answer these questions:
-
-- Which traffic direction is being filtered, `in` or `out`?
-- Is management traffic sourced from a known jump host or management subnet?
-- Is there an explicit permit for required routing, DNS, NTP, monitoring, or
-  application traffic?
-- Are hit counters available from a safe test source?
-- Is there a rollback command and an active console or out-of-band path?
-
-Do not test reachability by removing firewall or ACL protections. Read counters,
-logs, and route state first.
-
-## Interface Hygiene
-
-```text
-interface GigabitEthernet0/1
- description UPLINK-TO-CORE
- switchport mode trunk
- switchport trunk allowed vlan 10,20,30
- switchport trunk native vlan 999
- no shutdown
-```
-
-Use clear descriptions, explicit switchport mode, and documented native VLANs.
-On routed interfaces, confirm the mask, peer addressing, and routing process
-before assuming link state means forwarding is correct.
-
-## Change-Window Verification
-
-Use before/after checks that match the actual change.
-
-```text
-show running-config | section interface GigabitEthernet0/1
-show interfaces GigabitEthernet0/1
-show logging | include GigabitEthernet0/1|changed state|line protocol
-show ip route <prefix>
-show ip access-lists <name>
-```
-
-For routing changes, also capture neighbor state and route tables before and
-after the change. For ACL changes, compare hit counters from a planned test
-source rather than relying on a generic ping.
-
-## Anti-Patterns
-
-- Applying a generated config without a device-specific diff.
-- Saving configuration before post-change checks pass.
-- Using a subnet mask where IOS expects a wildcard mask.
-- Applying an ACL to the wrong interface direction.
-- Troubleshooting by disabling ACLs, route policies, or authentication.
-- Pasting full configs into public tools without sanitizing secrets and topology.
-
-## See Also
-
-- Agent: `network-config-reviewer`
-- Agent: `network-troubleshooter`
-- Skill: `network-config-validation`
-- Skill: `network-interface-health`
+---
+name: cisco-ios-patterns
+description: Cisco IOS and IOS-XE review patterns for show commands, config hierarchy, wildcard masks, ACL placement, interface hygiene, and safe change-window verification.
+metadata:
+  origin: community
+---
+
+# Cisco IOS Patterns
+
+Use this skill when reviewing Cisco IOS or IOS-XE snippets, building a
+change-window checklist, or explaining how to collect evidence from a router or
+switch without making the incident worse.
+
+## When to Use
+
+- Reviewing IOS or IOS-XE configuration before a planned change.
+- Choosing read-only `show` commands for troubleshooting.
+- Checking ACL wildcard masks and interface direction.
+- Explaining global, interface, routing process, and line configuration modes.
+- Verifying that a change landed in running config and was saved intentionally.
+
+## Operating Rules
+
+Treat IOS examples as patterns, not paste-ready production changes. Confirm the
+platform, interface names, current config, rollback path, and out-of-band access
+before making changes on a real device.
+
+Prefer this workflow:
+
+1. Capture current state with read-only commands.
+2. Review the exact candidate config.
+3. Confirm management access cannot be locked out.
+4. Apply the smallest change in a maintenance window.
+5. Re-read state, compare to the baseline, then save only after validation.
+
+## Mode Reference
+
+```text
+Router> enable
+Router# show running-config
+Router# configure terminal
+Router(config)# interface GigabitEthernet0/1
+Router(config-if)# description UPLINK-TO-CORE
+Router(config-if)# no shutdown
+Router(config-if)# exit
+Router(config)# end
+Router# show running-config interface GigabitEthernet0/1
+```
+
+`running-config` is active memory. `startup-config` is what survives reload.
+Do not save a change just because a command was accepted; validate behavior
+first, then use `copy running-config startup-config` if the change is approved.
+
+## Read-Only Collection
+
+```text
+show version
+show inventory
+show processes cpu sorted
+show memory statistics
+show logging
+show running-config | section line vty
+show running-config | section interface
+show running-config | section router bgp
+show ip interface brief
+show interfaces
+show interfaces status
+show vlan brief
+show mac address-table
+show spanning-tree
+show ip route
+show ip protocols
+show ip access-lists
+show route-map
+show ip prefix-list
+```
+
+Collect the specific section you need instead of dumping full config into a
+ticket when the config may contain secrets, customer names, or private topology.
+
+## Wildcard Masks
+
+IOS ACL and many routing statements use wildcard masks, not subnet masks.
+
+```text
+Subnet mask       Wildcard mask
+255.255.255.255   0.0.0.0
+255.255.255.252   0.0.0.3
+255.255.255.0     0.0.0.255
+255.255.0.0       0.0.255.255
+```
+
+Review wildcard masks before deployment. A subnet mask accidentally used as a
+wildcard can match far more traffic than intended.
+
+```text
+ip access-list extended WEB-IN
+  10 permit tcp 192.0.2.0 0.0.0.255 any eq 443
+  999 deny ip any any log
+```
+
+Every ACL has an implicit deny at the end. Add an explicit logged deny when the
+operational goal includes observing misses, and confirm logging volume is safe.
+
+## ACL Placement Review
+
+Before applying an ACL to an interface, answer these questions:
+
+- Which traffic direction is being filtered, `in` or `out`?
+- Is management traffic sourced from a known jump host or management subnet?
+- Is there an explicit permit for required routing, DNS, NTP, monitoring, or
+  application traffic?
+- Are hit counters available from a safe test source?
+- Is there a rollback command and an active console or out-of-band path?
+
+Do not test reachability by removing firewall or ACL protections. Read counters,
+logs, and route state first.
+
+## Interface Hygiene
+
+```text
+interface GigabitEthernet0/1
+ description UPLINK-TO-CORE
+ switchport mode trunk
+ switchport trunk allowed vlan 10,20,30
+ switchport trunk native vlan 999
+ no shutdown
+```
+
+Use clear descriptions, explicit switchport mode, and documented native VLANs.
+On routed interfaces, confirm the mask, peer addressing, and routing process
+before assuming link state means forwarding is correct.
+
+## Change-Window Verification
+
+Use before/after checks that match the actual change.
+
+```text
+show running-config | section interface GigabitEthernet0/1
+show interfaces GigabitEthernet0/1
+show logging | include GigabitEthernet0/1|changed state|line protocol
+show ip route <prefix>
+show ip access-lists <name>
+```
+
+For routing changes, also capture neighbor state and route tables before and
+after the change. For ACL changes, compare hit counters from a planned test
+source rather than relying on a generic ping.
+
+## Anti-Patterns
+
+- Applying a generated config without a device-specific diff.
+- Saving configuration before post-change checks pass.
+- Using a subnet mask where IOS expects a wildcard mask.
+- Applying an ACL to the wrong interface direction.
+- Troubleshooting by disabling ACLs, route policies, or authentication.
+- Pasting full configs into public tools without sanitizing secrets and topology.
+
+## See Also
+
+- Agent: `network-config-reviewer`
+- Agent: `network-troubleshooter`
+- Skill: `network-config-validation`
+- Skill: `network-interface-health`

package/skills/ck/SKILL.md

@@ -1,148 +1,148 @@
----
-name: ck
-description: Persistent per-project memory for Claude Code. Auto-loads project context on session start, tracks sessions with git activity, and writes to native memory. Commands run deterministic Node.js scripts — behavior is consistent across model versions.
-metadata:
-  origin: community
-version: 2.0.0
-author: sreedhargs89
-repo: https://github.com/sreedhargs89/context-keeper
----
-
-# ck — Context Keeper
-
-You are the **Context Keeper** assistant. When the user invokes any `/ck:*` command,
-run the corresponding Node.js script and present its stdout to the user verbatim.
-Scripts live at: `~/.claude/skills/ck/commands/` (expand `~` with `$HOME`).
-
----
-
-## Data Layout
-
-```
-~/.claude/ck/
-├── projects.json              ← path → {name, contextDir, lastUpdated}
-└── contexts/<name>/
-    ├── context.json           ← SOURCE OF TRUTH (structured JSON, v2)
-    └── CONTEXT.md             ← generated view — do not hand-edit
-```
-
----
-
-## Commands
-
-### `/ck:init` — Register a Project
-```bash
-node "$HOME/.claude/skills/ck/commands/init.mjs"
-```
-The script outputs JSON with auto-detected info. Present it as a confirmation draft:
-```
-Here's what I found — confirm or edit anything:
-Project:     <name>
-Description: <description>
-Stack:       <stack>
-Goal:        <goal>
-Do-nots:     <constraints or "None">
-Repo:        <repo or "none">
-```
-Wait for user approval. Apply any edits. Then pipe confirmed JSON to save.mjs --init:
-```bash
-echo '<confirmed-json>' | node "$HOME/.claude/skills/ck/commands/save.mjs" --init
-```
-Confirmed JSON schema: `{"name":"...","path":"...","description":"...","stack":["..."],"goal":"...","constraints":["..."],"repo":"..." }`
-
----
-
-### `/ck:save` — Save Session State
-**This is the only command requiring LLM analysis.** Analyze the current conversation:
-- `summary`: one sentence, max 10 words, what was accomplished
-- `leftOff`: what was actively being worked on (specific file/feature/bug)
-- `nextSteps`: ordered array of concrete next steps
-- `decisions`: array of `{what, why}` for decisions made this session
-- `blockers`: array of current blockers (empty array if none)
-- `goal`: updated goal string **only if it changed this session**, else omit
-
-Show a draft summary to the user: `"Session: '<summary>' — save this? (yes / edit)"`
-Wait for confirmation. Then pipe to save.mjs:
-```bash
-echo '<json>' | node "$HOME/.claude/skills/ck/commands/save.mjs"
-```
-JSON schema (exact): `{"summary":"...","leftOff":"...","nextSteps":["..."],"decisions":[{"what":"...","why":"..."}],"blockers":["..."]}`
-Display the script's stdout confirmation verbatim.
-
----
-
-### `/ck:resume [name|number]` — Full Briefing
-```bash
-node "$HOME/.claude/skills/ck/commands/resume.mjs" [arg]
-```
-Display output verbatim. Then ask: "Continue from here? Or has anything changed?"
-If user reports changes → run `/ck:save` immediately.
-
----
-
-### `/ck:info [name|number]` — Quick Snapshot
-```bash
-node "$HOME/.claude/skills/ck/commands/info.mjs" [arg]
-```
-Display output verbatim. No follow-up question.
-
----
-
-### `/ck:list` — Portfolio View
-```bash
-node "$HOME/.claude/skills/ck/commands/list.mjs"
-```
-Display output verbatim. If user replies with a number or name → run `/ck:resume`.
-
----
-
-### `/ck:forget [name|number]` — Remove a Project
-First resolve the project name (run `/ck:list` if needed).
-Ask: `"This will permanently delete context for '<name>'. Are you sure? (yes/no)"`
-If yes:
-```bash
-node "$HOME/.claude/skills/ck/commands/forget.mjs" [name]
-```
-Display confirmation verbatim.
-
----
-
-### `/ck:migrate` — Convert v1 Data to v2
-```bash
-node "$HOME/.claude/skills/ck/commands/migrate.mjs"
-```
-For a dry run first:
-```bash
-node "$HOME/.claude/skills/ck/commands/migrate.mjs" --dry-run
-```
-Display output verbatim. Migrates all v1 CONTEXT.md + meta.json files to v2 context.json.
-Originals are backed up as `meta.json.v1-backup` — nothing is deleted.
-
----
-
-## SessionStart Hook
-
-The hook at `~/.claude/skills/ck/hooks/session-start.mjs` must be registered in
-`~/.claude/settings.json` to auto-load project context on session start:
-
-```json
-{
-  "hooks": {
-    "SessionStart": [
-      { "hooks": [{ "type": "command", "command": "node \"~/.claude/skills/ck/hooks/session-start.mjs\"" }] }
-    ]
-  }
-}
-```
-
-The hook injects ~100 tokens per session (compact 5-line summary). It also detects
-unsaved sessions, git activity since last save, and goal mismatches vs CLAUDE.md.
-
----
-
-## Rules
-- Always expand `~` as `$HOME` in Bash calls.
-- Commands are case-insensitive: `/CK:SAVE`, `/ck:save`, `/Ck:Save` all work.
-- If a script exits with code 1, display its stdout as an error message.
-- Never edit `context.json` or `CONTEXT.md` directly — always use the scripts.
-- If `projects.json` is malformed, tell the user and offer to reset it to `{}`.
+---
+name: ck
+description: Persistent per-project memory for Claude Code. Auto-loads project context on session start, tracks sessions with git activity, and writes to native memory. Commands run deterministic Node.js scripts — behavior is consistent across model versions.
+metadata:
+  origin: community
+version: 2.0.0
+author: sreedhargs89
+repo: https://github.com/sreedhargs89/context-keeper
+---
+
+# ck — Context Keeper
+
+You are the **Context Keeper** assistant. When the user invokes any `/ck:*` command,
+run the corresponding Node.js script and present its stdout to the user verbatim.
+Scripts live at: `~/.claude/skills/ck/commands/` (expand `~` with `$HOME`).
+
+---
+
+## Data Layout
+
+```
+~/.claude/ck/
+├── projects.json              ← path → {name, contextDir, lastUpdated}
+└── contexts/<name>/
+    ├── context.json           ← SOURCE OF TRUTH (structured JSON, v2)
+    └── CONTEXT.md             ← generated view — do not hand-edit
+```
+
+---
+
+## Commands
+
+### `/ck:init` — Register a Project
+```bash
+node "$HOME/.claude/skills/ck/commands/init.mjs"
+```
+The script outputs JSON with auto-detected info. Present it as a confirmation draft:
+```
+Here's what I found — confirm or edit anything:
+Project:     <name>
+Description: <description>
+Stack:       <stack>
+Goal:        <goal>
+Do-nots:     <constraints or "None">
+Repo:        <repo or "none">
+```
+Wait for user approval. Apply any edits. Then pipe confirmed JSON to save.mjs --init:
+```bash
+echo '<confirmed-json>' | node "$HOME/.claude/skills/ck/commands/save.mjs" --init
+```
+Confirmed JSON schema: `{"name":"...","path":"...","description":"...","stack":["..."],"goal":"...","constraints":["..."],"repo":"..." }`
+
+---
+
+### `/ck:save` — Save Session State
+**This is the only command requiring LLM analysis.** Analyze the current conversation:
+- `summary`: one sentence, max 10 words, what was accomplished
+- `leftOff`: what was actively being worked on (specific file/feature/bug)
+- `nextSteps`: ordered array of concrete next steps
+- `decisions`: array of `{what, why}` for decisions made this session
+- `blockers`: array of current blockers (empty array if none)
+- `goal`: updated goal string **only if it changed this session**, else omit
+
+Show a draft summary to the user: `"Session: '<summary>' — save this? (yes / edit)"`
+Wait for confirmation. Then pipe to save.mjs:
+```bash
+echo '<json>' | node "$HOME/.claude/skills/ck/commands/save.mjs"
+```
+JSON schema (exact): `{"summary":"...","leftOff":"...","nextSteps":["..."],"decisions":[{"what":"...","why":"..."}],"blockers":["..."]}`
+Display the script's stdout confirmation verbatim.
+
+---
+
+### `/ck:resume [name|number]` — Full Briefing
+```bash
+node "$HOME/.claude/skills/ck/commands/resume.mjs" [arg]
+```
+Display output verbatim. Then ask: "Continue from here? Or has anything changed?"
+If user reports changes → run `/ck:save` immediately.
+
+---
+
+### `/ck:info [name|number]` — Quick Snapshot
+```bash
+node "$HOME/.claude/skills/ck/commands/info.mjs" [arg]
+```
+Display output verbatim. No follow-up question.
+
+---
+
+### `/ck:list` — Portfolio View
+```bash
+node "$HOME/.claude/skills/ck/commands/list.mjs"
+```
+Display output verbatim. If user replies with a number or name → run `/ck:resume`.
+
+---
+
+### `/ck:forget [name|number]` — Remove a Project
+First resolve the project name (run `/ck:list` if needed).
+Ask: `"This will permanently delete context for '<name>'. Are you sure? (yes/no)"`
+If yes:
+```bash
+node "$HOME/.claude/skills/ck/commands/forget.mjs" [name]
+```
+Display confirmation verbatim.
+
+---
+
+### `/ck:migrate` — Convert v1 Data to v2
+```bash
+node "$HOME/.claude/skills/ck/commands/migrate.mjs"
+```
+For a dry run first:
+```bash
+node "$HOME/.claude/skills/ck/commands/migrate.mjs" --dry-run
+```
+Display output verbatim. Migrates all v1 CONTEXT.md + meta.json files to v2 context.json.
+Originals are backed up as `meta.json.v1-backup` — nothing is deleted.
+
+---
+
+## SessionStart Hook
+
+The hook at `~/.claude/skills/ck/hooks/session-start.mjs` must be registered in
+`~/.claude/settings.json` to auto-load project context on session start:
+
+```json
+{
+  "hooks": {
+    "SessionStart": [
+      { "hooks": [{ "type": "command", "command": "node \"~/.claude/skills/ck/hooks/session-start.mjs\"" }] }
+    ]
+  }
+}
+```
+
+The hook injects ~100 tokens per session (compact 5-line summary). It also detects
+unsaved sessions, git activity since last save, and goal mismatches vs CLAUDE.md.
+
+---
+
+## Rules
+- Always expand `~` as `$HOME` in Bash calls.
+- Commands are case-insensitive: `/CK:SAVE`, `/ck:save`, `/Ck:Save` all work.
+- If a script exits with code 1, display its stdout as an error message.
+- Never edit `context.json` or `CONTEXT.md` directly — always use the scripts.
+- If `projects.json` is malformed, tell the user and offer to reset it to `{}`.