@nemus-cli/nemus 0.2.5 → 0.2.7

package/skills/nemus/references/mcp.md

@@ -1,11 +1,5 @@
 # MCP Server
 
-Manage the MCP (Model Context Protocol) server integration with Claude Code.
-
-## Commands
-
-### Install
-
 Register the Nemus MCP server with Claude Code:
 ```bash
 nemus mcp install
@@ -13,15 +7,11 @@ nemus mcp install
 
 This also installs shell integration, permission sync hooks, and workspace skills.
 
-### Uninstall
-
 Remove the MCP server registration:
 ```bash
 nemus mcp uninstall
 ```
 
-### Upgrade
-
 Update hooks and skills without re-registering the MCP server:
 ```bash
 nemus mcp upgrade
@@ -29,8 +19,6 @@ nemus mcp upgrade
 
 Use after updating the Nemus package.
 
-### Status
-
 Check if the MCP server is registered:
 ```bash
 nemus mcp status
@@ -41,4 +29,3 @@ nemus mcp status
 When installed, Claude Code gains access to Nemus tools:
 - `create-workspace`, `list-workspaces`, `workspace-status`, etc.
 - Enables natural language workspace management via `nemus -- <prompt>`
-

package/skills/nemus/references/remove-repo.md

@@ -1,9 +1,5 @@
 # Remove Repo
 
-Remove a repository instance from a workspace.
-
-## Instructions
-
 1. Warn the user about any uncommitted changes before removing.
 
 2. Run the command:
@@ -20,4 +16,3 @@ Remove a repository instance from a workspace.
 | `--workspace <name>` | `-w` | Target workspace |
 | `--repos <dir,...>` | `-r` | Comma-separated directory names to remove |
 | `--yes` | `-y` | Skip confirmation prompt |
-

package/skills/nemus/references/run-command.md

@@ -1,9 +1,5 @@
 # Run Command
 
-Run a shell command across all repositories in a workspace (3 concurrent, 5 minute timeout per repo).
-
-## Instructions
-
 ```bash
 nemus run <workspace> <command>
 ```
@@ -37,4 +33,3 @@ Shows per-repo results:
 - Summary count of successes and failures
 
 Exits with code 1 if any repo failed.
-

package/skills/nemus/references/search-repos.md

@@ -1,9 +1,5 @@
 # Search Repos
 
-Search organization repositories by name or description using fuzzy matching.
-
-## Instructions
-
 1. Run:
    ```bash
    nemus cache search <query>
@@ -17,4 +13,3 @@ Search organization repositories by name or description using fuzzy matching.
 3. If the user is looking for repos to add to a workspace, suggest:
    - `nemus create` to create a new workspace with selected repos
    - `nemus update` to add repos to an existing workspace
-

package/skills/nemus/references/sessions.md

@@ -1,9 +1,5 @@
 # Sessions
 
-Pick a workspace with an active Claude Code session and resume it.
-
-## Instructions
-
 Interactive only — displays a fuzzy-searchable list of workspaces with sessions:
 ```bash
 nemus sessions
@@ -14,9 +10,6 @@ Alias:
 w ses
 ```
 
-## How It Works
-
 1. Scans for Claude Code sessions across all workspaces
 2. Shows them sorted by last active time
 3. User picks one → terminal CDs to that workspace and resumes the Claude session
-

package/skills/nemus/references/suite-create.md

@@ -1,9 +1,5 @@
 # Suite Create
 
-Create a new suite (reusable collection of repositories) that can be used to quickly set up workspaces.
-
-## Instructions
-
 1. In interactive mode:
    ```bash
    nemus suite create
@@ -15,4 +11,3 @@ Create a new suite (reusable collection of repositories) that can be used to qui
    ```
 
 3. After creation, confirm with the suite name and repo count.
-

package/skills/nemus/references/suite-delete.md

@@ -1,9 +1,5 @@
 # Suite Delete
 
-Delete a saved suite.
-
-## Instructions
-
 1. In interactive mode:
    ```bash
    nemus suite delete
@@ -15,4 +11,3 @@ Delete a saved suite.
    ```
 
 3. Confirm deletion.
-

package/skills/nemus/references/suite-export.md

@@ -1,9 +1,5 @@
 # Suite Export
 
-Export one or all suites to a JSON file for sharing.
-
-## Instructions
-
 1. Export all suites:
    ```bash
    nemus suite export ./suites.json
@@ -12,4 +8,3 @@ Export one or all suites to a JSON file for sharing.
 2. In interactive mode, you'll be prompted to choose a single suite or all.
 
 3. Share the exported file with teammates who can import it with `nemus suite import`.
-

package/skills/nemus/references/suite-import.md

@@ -1,9 +1,5 @@
 # Suite Import
 
-Import suites from a JSON file (exported by `nemus suite export`).
-
-## Instructions
-
 1. Run:
    ```bash
    nemus suite import <file-path>
@@ -12,4 +8,3 @@ Import suites from a JSON file (exported by `nemus suite export`).
 2. Existing suites with the same name will be skipped by default.
 
 3. After import, verify with `nemus suite list`.
-

package/skills/nemus/references/suite-use.md

@@ -1,9 +1,5 @@
 # Suite Use
 
-Create a new workspace from a saved suite.
-
-## Instructions
-
 1. In interactive mode:
    ```bash
    nemus suite use
@@ -20,4 +16,3 @@ Create a new workspace from a saved suite.
    - Set up Claude Code integration
 
 4. After creation, suggest `nemus status <workspace>` to verify.
-

package/skills/nemus/references/switch-branch.md

@@ -1,9 +1,5 @@
 # Switch Branch
 
-Switch all repositories in a workspace to a specified branch.
-
-## Instructions
-
 ```bash
 nemus branch switch --workspace <name> --branch <branch-name>
 ```
@@ -18,4 +14,3 @@ nemus branch switch --workspace <name> --branch <branch-name>
 If some repos fail to switch (due to uncommitted changes), suggest:
 - Committing or stashing changes first
 - Using `nemus status <name>` to check the state
-

package/skills/nemus/references/update-cache.md

@@ -1,9 +1,5 @@
 # Update Cache
 
-Force refresh the GitHub repository cache so newly added repos become searchable.
-
-## Instructions
-
 1. Run:
    ```bash
    nemus cache refresh
@@ -16,4 +12,3 @@ Force refresh the GitHub repository cache so newly added repos become searchable
 2. Report the result (number of repos cached, etc.).
 
 3. Suggest using `nemus cache search <query>` or `nemus cache list` to browse the updated list.
-

package/skills/nemus/references/update-workspace.md

@@ -1,9 +1,5 @@
 # Update Workspace
 
-Add more repositories to an existing workspace.
-
-## Instructions
-
 1. Run the command with flags (non-interactive):
    ```bash
    nemus update --workspace <name> --repos <r1,r2,...>
@@ -23,8 +19,6 @@ Add more repositories to an existing workspace.
 | `--workspace <name>` | `-w` | Target workspace |
 | `--repos <r1,r2,...>` | `-r` | Comma-separated repo names to add. Use `repo:suffix` to add the same repo again under a separate folder. |
 
-## Adding the same repo more than once (instances)
-
 The same repository can live in a workspace multiple times under different
 folders — useful for comparing branches/versions side by side, or keeping a
 second checkout instead of a `git worktree` (which `nemus status`/`nemus sync` do NOT
@@ -43,4 +37,3 @@ instance is tracked independently by `nemus status` and `nemus sync` and is labe
 > Do NOT use `git worktree` inside a workspace to get a second checkout of a
 > tracked repo — worktrees are invisible to `nemus status`/`nemus sync`. Use
 > `nemus update --repos <repo>:<suffix>` instead.
-

package/skills/nemus/references/workspace-cleanup.md

@@ -1,9 +1,5 @@
 # Workspace Cleanup
 
-Remove node_modules and build artifacts from all repos in a workspace to free disk space.
-
-## Instructions
-
 ```bash
 nemus cleanup <workspace> --all --yes
 ```
@@ -26,4 +22,3 @@ nemus cleanup <workspace> --git-clean --yes
 | `--yes` / `-y` | Skip confirmation prompt |
 
 Remind the user they'll need to run `npm install` before building again.
-

package/skills/nemus/references/workspace-diff.md

@@ -1,9 +1,5 @@
 # Workspace Diff
 
-Show diff summary (staged/unstaged file counts, insertions, deletions) for all repos in a workspace.
-
-## Instructions
-
 1. If no workspace is specified, run `nemus list` and ask which one.
 
 2. Run:
@@ -21,4 +17,3 @@ Show diff summary (staged/unstaged file counts, insertions, deletions) for all r
    - Which files changed
 
 4. If the user wants full diff content, they can pipe through `less` or redirect to a file.
-

package/skills/nemus/references/workspace-doctor.md

@@ -1,9 +1,5 @@
 # Workspace Doctor
 
-Run comprehensive health checks on a workspace and return a health score (0-100).
-
-## Instructions
-
 1. If no workspace is specified, run `nemus list` and ask which one.
 
 2. Run:
@@ -20,4 +16,3 @@ Run comprehensive health checks on a workspace and return a health score (0-100)
    - `nemus sync` for outdated repos
    - `nemus cleanup` for disk space issues
    - `nemus branch create` or `nemus branch switch` for branch inconsistencies
-

package/skills/nemus/references/workspace-info.md

@@ -1,9 +1,5 @@
 # Workspace Info
 
-Get detailed metadata for a workspace including all repository info and status.
-
-## Instructions
-
 There is no dedicated `nemus info` CLI command. To get workspace information, combine:
 
 1. **List workspaces** to see all available:
@@ -27,4 +23,3 @@ There is no dedicated `nemus info` CLI command. To get workspace information, co
    ```
 
 The MCP tool `workspace-info` provides detailed metadata programmatically.
-

package/skills/nemus/references/workspace-status.md

@@ -1,9 +1,5 @@
 # Workspace Status
 
-Show git status (branch, clean/dirty, ahead/behind) for all repositories in a workspace.
-
-## Instructions
-
 ```bash
 nemus status <workspace>
 ```
@@ -28,4 +24,3 @@ Displays a table per repository showing:
 - **Modified files** count
 
 Plus a summary: clean repos, dirty repos, needs push, needs pull.
-

package/skills/nemus/references/workspace-sync.md

@@ -1,9 +1,5 @@
 # Workspace Sync
 
-Pull latest changes for all repositories in a workspace. Skips repos with uncommitted changes.
-
-## Instructions
-
 ```bash
 nemus sync <workspace>
 ```
@@ -19,4 +15,3 @@ Report results per repo:
 - Any repos that failed
 
 If some repos were skipped, suggest committing or stashing changes first, then re-run `nemus sync <name>`.
-

package/skills/refresh-workspace-docs.md

@@ -3,10 +3,6 @@ name: refresh-workspace-docs
 description: Refresh the per-repo documentation embedded in a workspace's context file (AGENTS.md / .claude.md). Use when a workspace was created a while ago and its repos have since received updates to their README, AGENTS.md, or CLAUDE.md files, so the embedded copies in the workspace context are stale.
 ---
 
-# Refresh Workspace Docs
-
-Each repo's `AGENTS.md`/`CLAUDE.md` is embedded into the workspace context file's `## Per-Repository Context` section at creation time — a snapshot that does **not** auto-update. Refresh it in two steps:
-
 ```bash
 nemus sync <workspace>       # 1. git pull every repo so on-disk docs are current
 nemus migrate                # 2. rebuild the Per-Repository Context section from disk

package/skills/remove-repo.md

@@ -3,12 +3,6 @@ name: remove-repo
 description: Remove a repository from a workspace
 ---
 
-# Remove Repo
-
-Remove a repository from a workspace.
-
-## Running
-
 ```bash
 nemus remove-repo --workspace <name> --repo <repo-name> --yes
 ```
@@ -18,8 +12,6 @@ Or interactively:
 nemus remove-repo
 ```
 
-## Important Notes
-
 - This removes the repo directory from the workspace
 - The repo is not deleted from GitHub, only removed locally
 - The workspace metadata is updated to reflect the removal

package/skills/run-command.md

@@ -3,12 +3,6 @@ name: run-command
 description: Run a shell command across all repos in a workspace
 ---
 
-# Run Command
-
-Run a shell command across all repos in a workspace.
-
-## Running
-
 ```bash
 nemus run <workspace-name> "<command>"
 ```
@@ -17,4 +11,3 @@ Example:
 ```bash
 nemus run my-workspace "git log --oneline -5"
 ```
-

package/skills/save-context.md

@@ -3,26 +3,16 @@ name: save-context
 description: Save progress summary to workspace (persists across /clear and session restarts). Use when you want to preserve important context, findings, or progress before clearing conversation history.
 ---
 
-# Save Context
-
-Save a progress summary or important context to the workspace. This persists in `CONTEXT.md` and survives `/clear`, session restarts, and agent switches.
-
-## When to Use
-
 - Before `/clear` to preserve progress
 - After completing a significant milestone
 - To leave notes for the next session
 - When switching between tasks in the same workspace
 
-## Using the MCP Tool (Claude Code)
-
 Call `mcp__nemus__save-context` with:
 - `workspace` (string): the workspace name
 - `content` (string): markdown content to save
 - `append` (boolean, optional): true to append, false to replace (default: false)
 
-## Using the CLI (any agent)
-
 ```bash
 # Replace existing context
 nemus save-context -m "Completed auth refactor. Next: update payment service endpoints."
@@ -37,8 +27,6 @@ nemus save-context -f progress-notes.md
 echo "summary here" | nemus save-context
 ```
 
-## What to Save
-
 Good context summaries include:
 - **What was done** — completed tasks, merged PRs
 - **Current state** — what's working, what's broken
@@ -53,4 +41,4 @@ Good context summaries include:
 
 All services passing CI. Auth migration is complete for internal services.
 External API consumers still use legacy tokens (tracked in JIRA PAY-123).
-
+```

package/skills/search-repos.md

@@ -3,23 +3,14 @@ name: search-repos
 description: Search org repositories by name or description
 ---
 
-# Search Repos
-
-Search for repositories in the GitHub organization.
-
-## Searching
-
 ```bash
 nemus cache search <keyword>
 ```
 
 This searches the cached list of org repos by name. Results show repo name and description.
 
-## If Cache is Empty
-
 ```bash
 nemus cache refresh
 ```
 
 Then search again.
-

package/skills/snapshot-list.md

@@ -3,13 +3,6 @@ name: snapshot-list
 description: List all saved workspace snapshots
 ---
 
-# Snapshot List
-
-List all saved workspace snapshots.
-
-## Running
-
 ```bash
 nemus history
 ```
-

package/skills/snapshot-save.md

@@ -3,10 +3,6 @@ name: snapshot-save
 description: Save a snapshot of the current workspace state
 ---
 
-# Snapshot Save
-
-Snapshots are automatically saved by Nemus operations (create, update, delete, etc.). There is no separate snapshot command — the history command shows past operations:
-
 ```bash
 nemus history
 ```

package/skills/switch-branch.md

@@ -3,13 +3,6 @@ name: switch-branch
 description: Switch all repos in a workspace to a specified branch
 ---
 
-# Switch Branch
-
-Switch all repos in a workspace to a specified branch.
-
-## Running
-
 ```bash
 nemus branch switch <workspace-name> <branch-name>
 ```
-

package/skills/update-cache.md

@@ -3,19 +3,11 @@ name: update-cache
 description: Force refresh the GitHub repository cache
 ---
 
-# Update Cache
-
-Force refresh the GitHub repository cache.
-
-## Running
-
 ```bash
 nemus cache refresh
 ```
 
 This fetches the latest list of repositories from the GitHub org and updates the local cache.
 
-## When to Use
-
 - When `nemus cache search` doesn't find a recently created repo
 - Periodically to keep the cache fresh (auto-refreshes daily)

package/skills/update-workspace.md

@@ -3,16 +3,10 @@ name: update-workspace
 description: Add one or more repositories to an existing workspace. ALWAYS use this skill — never run `git clone` directly — when the user asks to add, clone, include, or pull a new repo into the current workspace. Triggers on phrases like "add repo X", "include X in this workspace", "I need X here", "clone X into workspace", "add a service".
 ---
 
-# Update Workspace
-
 > **CRITICAL**: NEVER use `git clone` directly to add repositories to a workspace.
 > Always use `nemus update` — it registers the repo in workspace metadata, updates
 > the context file, and keeps `nemus status`/`nemus sync` working correctly.
 
-Add more repositories to an existing workspace.
-
-## Resolving the Workspace
-
 If the user hasn't specified a workspace, run:
 ```bash
 nemus list 2>&1 | cat
@@ -23,8 +17,6 @@ Or to see what's in a specific workspace (from inside the workspace directory):
 cat .workspace-meta.json
 ```
 
-## Resolving Repositories
-
 If the user hasn't specified which repos to add, help them discover:
 ```bash
 nemus cache search <keyword>
@@ -35,15 +27,11 @@ To see what's already in the workspace (avoid adding duplicates):
 cat .workspace-meta.json | jq '.repositories[].name'
 ```
 
-## Adding Repos
-
 Run the update command non-interactively:
 ```bash
 nemus update --workspace <name> --repos <repo1,repo2,...> --yes
 ```
 
-### Adding the same repo more than once (instances)
-
 Append `:suffix` to a repo name to add it again under a separate folder
 (`<repo>-<suffix>`) — e.g. a second checkout for another branch instead of a
 `git worktree` (worktrees are invisible to `nemus status`/`nemus sync`):
@@ -52,4 +40,3 @@ nemus update --workspace <name> --repos casper:cas-101 --yes   # -> casper-cas-1
 ```
 Suffix = letters, numbers, hyphens, underscores. Each instance is tracked
 independently by `nemus status`/`nemus sync`.
-

package/skills/workspace-cleanup.md

@@ -3,13 +3,6 @@ name: workspace-cleanup
 description: Remove node_modules and build artifacts to free disk space
 ---
 
-# Workspace Cleanup
-
-Remove node_modules and build artifacts to free disk space.
-
-## Running
-
 ```bash
 nemus cleanup <workspace-name>
 ```
-

package/skills/workspace-diff.md

@@ -3,12 +3,6 @@ name: workspace-diff
 description: Show diff summary for all repos in a workspace
 ---
 
-# Workspace Diff
-
-Show diff summary across all repos in a workspace.
-
-## Running
-
 ```bash
 nemus diff <workspace-name>
 ```
@@ -17,4 +11,3 @@ Or for the current workspace:
 ```bash
 nemus diff
 ```
-

package/skills/workspace-doctor.md

@@ -3,12 +3,6 @@ name: workspace-doctor
 description: Run health checks on a workspace
 ---
 
-# Workspace Doctor
-
-Run health checks on a workspace.
-
-## Running
-
 ```bash
 nemus doctor <workspace-name>
 ```
@@ -17,4 +11,3 @@ Or for the current workspace:
 ```bash
 nemus doctor
 ```
-

package/skills/workspace-info.md

@@ -3,19 +3,11 @@ name: workspace-info
 description: Get detailed metadata for a workspace
 ---
 
-# Workspace Info
-
-Get detailed metadata for a workspace including all repository info, tags, and disk path.
-
-## Resolving the Workspace
-
 If the user hasn't specified a workspace name, list them:
 ```bash
 nemus list 2>&1 | cat
 ```
 
-## Getting Info
-
 Read the workspace metadata file (path is relative to the workspace directory):
 ```bash
 cat <workspace-path>/.workspace-meta.json
@@ -25,4 +17,3 @@ The workspace path can be found by checking the current directory or using:
 ```bash
 nemus status <workspace-name>
 ```
-

package/skills/workspace-status.md

@@ -3,12 +3,6 @@ name: workspace-status
 description: Show git status for all repos in a workspace
 ---
 
-# Workspace Status
-
-Show git status across all repos in a workspace.
-
-## Running
-
 ```bash
 nemus status <workspace-name>
 ```
@@ -17,4 +11,3 @@ Or for the current workspace:
 ```bash
 nemus status
 ```
-

package/skills/workspace-sync.md

@@ -3,12 +3,6 @@ name: workspace-sync
 description: Git pull all repos in a workspace
 ---
 
-# Workspace Sync
-
-Pull latest changes for all repos in a workspace.
-
-## Running
-
 ```bash
 nemus sync <workspace-name>
 ```
@@ -17,4 +11,3 @@ Or for the current workspace:
 ```bash
 nemus sync
 ```
-