@nemus-cli/nemus 0.2.4 → 0.2.6

package/skills/{workspace-manager → nemus}/references/mcp.md

@@ -1,35 +1,23 @@
 # MCP Server
 
-Manage the MCP (Model Context Protocol) server integration with Claude Code.
-
-## Commands
-
-### Install
-
-Register the workspace-manager MCP server with Claude Code:
+Register the Nemus MCP server with Claude Code:
 ```bash
 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
 ```
 
-Use after updating the workspace-manager package.
-
-### Status
+Use after updating the Nemus package.
 
 Check if the MCP server is registered:
 ```bash
@@ -38,12 +26,6 @@ nemus mcp status
 
 ## What MCP Provides
 
-When installed, Claude Code gains access to workspace-manager tools:
+When installed, Claude Code gains access to Nemus tools:
 - `create-workspace`, `list-workspaces`, `workspace-status`, etc.
 - Enables natural language workspace management via `nemus -- <prompt>`
-
-## When to Suggest
-
-- After installing or upgrading workspace-manager
-- When Claude Code doesn't seem to have workspace tools
-- When `nemus -- <prompt>` fails to find MCP tools

package/skills/{workspace-manager → 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,7 +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 |
-
-## Success Criteria
-
-- The specified repo directory is removed from the workspace after user confirmation.

package/skills/{workspace-manager → nemus}/references/run-command.md

@@ -1,16 +1,12 @@
 # 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>
 ```
 
 Alias:
 ```bash
-w r <workspace> <command>
+nem r <workspace> <command>
 ```
 
 Without a workspace name, prompts interactively:
@@ -37,8 +33,3 @@ Shows per-repo results:
 - Summary count of successes and failures
 
 Exits with code 1 if any repo failed.
-
-## Success Criteria
-
-- Command is executed in all repos and per-repo success/failure is reported.
-- stdout and stderr from each repo are clearly displayed.

package/skills/{workspace-manager → 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,8 +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
-
-## Success Criteria
-
-- Matching repos are listed with name, description, and URL.
-- Follow-up action (create or update workspace) is suggested if appropriate.

package/skills/{workspace-manager → 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,14 +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
-
-## When to Suggest
-
-- User asks to "continue where I left off"
-- User wants to resume work on a previous workspace
-- User asks about their recent Claude sessions

package/skills/{workspace-manager → 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,8 +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.
-
-## Success Criteria
-
-- Suite is saved with the specified name and repos.
-- Suite appears in `nemus suite list`.

package/skills/{workspace-manager → 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,7 +11,3 @@ Delete a saved suite.
    ```
 
 3. Confirm deletion.
-
-## Success Criteria
-
-- Suite is removed and no longer appears in `nemus suite list`.

package/skills/{workspace-manager → 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,8 +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`.
-
-## Success Criteria
-
-- JSON file is created with suite data.
-- File can be imported with `nemus suite import`.

package/skills/{workspace-manager → 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,8 +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`.
-
-## Success Criteria
-
-- Suites from the file are imported.
-- Imported suites appear in `nemus suite list`.

package/skills/{workspace-manager → 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,8 +16,3 @@ Create a new workspace from a saved suite.
    - Set up Claude Code integration
 
 4. After creation, suggest `nemus status <workspace>` to verify.
-
-## Success Criteria
-
-- Workspace is created with all suite repos cloned.
-- Post-clone hooks (if any) are executed.

package/skills/{workspace-manager → 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,8 +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
-
-## Success Criteria
-
-- All repos without uncommitted changes are switched to the target branch.
-- Repos that failed to switch are clearly reported with the reason.

package/skills/{workspace-manager → 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,7 +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.
-
-## Success Criteria
-
-- Cache is refreshed and the updated repo count is reported.

package/skills/{workspace-manager → 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,8 +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.
-
-## Success Criteria
-
-- All specified repos are cloned into the workspace.
-- User is informed of any repos skipped due to already existing.

package/skills/{workspace-manager → 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,8 +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.
-
-## Success Criteria
-
-- Selected directories are removed and disk space freed is reported.
-- User is reminded to re-run `npm install` before building.

package/skills/{workspace-manager → 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,7 +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.
-
-## Success Criteria
-
-- Per-repo diff summary is presented with file counts and line statistics.

package/skills/{workspace-manager → 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,8 +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
-
-## Success Criteria
-
-- Health score and per-check results are clearly presented.
-- Actionable remediation steps are provided for any failures or warnings.

package/skills/{workspace-manager → 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,7 +23,3 @@ There is no dedicated `nemus info` CLI command. To get workspace information, co
    ```
 
 The MCP tool `workspace-info` provides detailed metadata programmatically.
-
-## Success Criteria
-
-- User gets the workspace information they need through the appropriate command.

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

@@ -0,0 +1,26 @@
+# Workspace Status
+
+```bash
+nemus status <workspace>
+```
+
+Alias:
+```bash
+nem st <workspace>
+```
+
+Without a workspace name, prompts interactively:
+```bash
+nemus status
+```
+
+## Output
+
+Displays a table per repository showing:
+- **Repo name**
+- **Branch** (with detached HEAD warning)
+- **Status** — clean ✓ or modified/untracked count
+- **Ahead/Behind** — commits ahead/behind remote
+- **Modified files** count
+
+Plus a summary: clean repos, dirty repos, needs push, needs pull.

package/skills/{workspace-manager → 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,8 +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>`.
-
-## Success Criteria
-
-- All clean repos are pulled to latest.
-- User is informed of any skipped repos with uncommitted changes.

package/skills/refresh-workspace-docs.md

@@ -3,87 +3,11 @@ 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
-
-When a workspace is created, each repo's own `AGENTS.md` / `CLAUDE.md` is
-embedded into the workspace-level context file (`AGENTS.md` / `.claude.md`)
-under the **Per-Repository Context** section. Those embedded copies are a
-snapshot taken at creation time — they do **not** auto-update when the repo
-later receives new commits that change its README or agent docs.
-
-This skill refreshes that embedded content so the agent works from the
-latest per-repo guidance.
-
-## When to Use
-
-- A workspace was created days/weeks ago and the repos have since changed.
-- A repo's `AGENTS.md` / `CLAUDE.md` / `README.md` was updated upstream and
-  you want the workspace context to reflect it.
-- The agent seems to be following outdated repo-specific instructions.
-- After a teammate merges changes to a repo's documentation.
-
-## Workflow
-
-Two steps: **sync the repos to latest**, then **regenerate the context**.
-
-### 1. Pull the latest for every repo in the workspace
-
-```bash
-nemus sync <workspace-name>
-```
-
-This `git pull`s every repo so their on-disk `README.md`, `AGENTS.md`, and
-`CLAUDE.md` reflect the latest upstream content. (Omit the name to sync the
-current workspace.)
-
-### 2. Regenerate the workspace context
-
-```bash
-w migrate
-```
-
-`nemus migrate` re-reads each repo's context files from disk and **surgically
-updates only the `## Per-Repository Context` section** of the workspace
-`AGENTS.md` / `.claude.md`. Your own notes (the `## Notes` section, saved
-`CONTEXT.md`, etc.) are preserved untouched.
-
-Preview what would change first with:
-
 ```bash
-w migrate --dry-run
+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
 ```
 
-## What Gets Refreshed
-
-The `## Per-Repository Context` section is rebuilt from each repo's context
-file, discovered in this priority order (per repo, up to 2 directory levels
-deep for monorepo packages):
-
-1. `AGENTS.md`
-2. `.claude.md`
-3. `CLAUDE.md`
-
-Each repo's content is embedded with imperative scoping ("You MUST follow
-these rules whenever you work with files inside `<repo>/`") and placed near
-the top of the workspace context file so the agent weights it heavily.
-
-## Notes
-
-- This only refreshes **embedded** per-repo docs in the workspace context
-  file. The repos themselves are updated by `nemus sync` in step 1.
-- `nemus migrate` runs across **all** workspaces. That's safe and idempotent —
-  every workspace gets its per-repo section refreshed from current on-disk
-  content. Use `--dry-run` first if you want to see scope.
-- If a workspace has no repo-level context files, the section is omitted
-  (or removed if it previously existed).
-
-## Example
-
-```bash
-# Workspace 'payments' was created 3 weeks ago; partnerships-api has since
-# rewritten its AGENTS.md with new Jira board instructions.
-
-nemus sync payments        # pull latest — partnerships-api/AGENTS.md now current
-w migrate --dry-run    # preview: "payments: would embed per-repo context from 4 location(s)"
-w migrate              # apply — workspace AGENTS.md now has the new instructions
-```
+- Use `nemus migrate --dry-run` first to preview scope.
+- `nemus migrate` runs across **all** workspaces; it's idempotent and only touches the `## Per-Repository Context` section — your `## Notes` and `CONTEXT.md` are preserved.
+- Per repo it embeds the first of `AGENTS.md` → `.claude.md` → `CLAUDE.md` found (up to 2 dir levels deep). If none exist, the section is omitted.

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,7 +11,3 @@ Example:
 ```bash
 nemus run my-workspace "git log --oneline -5"
 ```
-
-## Presenting Results
-
-Report the output from each repo, clearly labeling which output comes from which repo.

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__workspace-manager__save-context` with:
+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
@@ -49,20 +37,8 @@ Good context summaries include:
 ## Example
 
 ```markdown
-## Progress
-
-- Refactored auth service to use JWT tokens (PR #42 merged)
-- Updated partnerships-api to call new auth endpoints
-- Fixed rate limiting bug in payment-gateway
-
 ## Current State
 
 All services passing CI. Auth migration is complete for internal services.
 External API consumers still use legacy tokens (tracked in JIRA PAY-123).
-
-## Next Steps
-
-1. Migrate external consumers to JWT (need coordination with partners team)
-2. Add monitoring dashboard for token refresh failures
-3. Remove legacy token support after 30-day deprecation window
 ```

package/skills/search-repos.md

@@ -3,29 +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.
-
-## Presenting Results
-
-Show matching repos with their names and descriptions. If the user wants to add repos to a workspace, suggest:
-```bash
-nemus update --workspace <name> --repos <repo1,repo2> --yes
-```

package/skills/snapshot-list.md

@@ -3,16 +3,6 @@ name: snapshot-list
 description: List all saved workspace snapshots
 ---
 
-# Snapshot List
-
-List all saved workspace snapshots.
-
-## Running
-
 ```bash
 nemus history
 ```
-
-## Presenting Results
-
-Show snapshot entries with timestamps and operation types.

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 workspace-manager operations (create, update, delete, etc.). There is no separate snapshot command — the history command shows past operations:
-
 ```bash
 nemus history
 ```