How do I install the Workspace Status skill?

Run npx skillmds@latest add tomevault-io/workspace-status in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Workspace Status safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Workspace Status?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Workspace Status free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Workspace Status?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Workspace Status by tomevault-io — Agent Skill

Name: Workspace Status
Author: tomevault-io

Workspace Status

Multi-repository workspace status overview and analysis. Use when checking workspace state, understanding repo boundaries, or before running git operations in multi-repo workspaces. Use when this capability is needed.

tomevault-io 58d9443 2 files · 3.1 KB Updated Sep 17, 2026

File contents

Workspace Status Command

Description

Multi-repository workspace status overview with comprehensive analysis.

Workflow

Always check current working directory and understand repository boundaries
Never assume single git repository when working in multi-repo workspace
Always verify which repository operations are targeting
Identify which specific repository changes belong to
Navigate to correct repository directory before running git operations
Treat each repository as separate entity with its own git state

Multi-Repository Handling

When working with staged changes, identify which specific repository they belong to
Provide clear indication of repository boundaries
Show status for each repository found in workspace
Highlight any cross-repository dependencies or conflicts

Error Prevention

Always ask for clarification when workspace structure is unclear
Confirm target repository before running git commands
Use non-destructive git commands first (git stash, git log) to understand situation

Output Format

Workspace: /path/to/workspace
Repositories: 3

Repository 1: /path/to/repo1
  Branch: main
  Status: clean
  Last commit: 2 hours ago
  Remote: origin/main

Repository 2: /path/to/repo2
  Branch: feature/new-feature
  Status: dirty
  Staged: 2 files
  Modified: 1 file
  Last commit: 1 hour ago
  Remote: origin/feature/new-feature

Repository 3: /path/to/repo3
  Branch: develop
  Status: clean
  Last commit: 3 hours ago
  Remote: origin/develop

Examples

# Check workspace status
/workspace-status

# Check specific workspace
/workspace-status /path/to/workspace

# Detailed status with file changes
/workspace-status --detailed

Features

Multi-repository detection
Cross-repository dependency analysis
Conflict detection and reporting
Workspace boundary identification
Git state analysis per repository

Integration

Works with all git commands
Integrates with PR workflow
Supports Linear issue tracking
Compatible with branch management

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: workspace-statusdescription: Multi-repository workspace status overview and analysis. Use when checking workspace state, understanding repo boundaries, or before running git operations in multi-repo workspaces. Use when this capability is needed.---# Workspace Status Command## DescriptionMulti-repository workspace status overview with comprehensive analysis.## Workflow1. Always check current working directory and understand repository boundaries2. Never assume single git repository when working in multi-repo workspace3. Always verify which repository operations are targeting4. Identify which specific repository changes belong to5. Navigate to correct repository directory before running git operations6. Treat each repository as separate entity with its own git state## Multi-Repository Handling- When working with staged changes, identify which specific repository they belong to- Provide clear indication of repository boundaries- Show status for each repository found in workspace- Highlight any cross-repository dependencies or conflicts## Error Prevention- Always ask for clarification when workspace structure is unclear- Confirm target repository before running git commands- Use non-destructive git commands first (git stash, git log) to understand situation## Output Format```Workspace: /path/to/workspaceRepositories: 3Repository 1: /path/to/repo1 Branch: main Status: clean Last commit: 2 hours ago Remote: origin/mainRepository 2: /path/to/repo2 Branch: feature/new-feature Status: dirty Staged: 2 files Modified: 1 file Last commit: 1 hour ago Remote: origin/feature/new-featureRepository 3: /path/to/repo3 Branch: develop Status: clean Last commit: 3 hours ago Remote: origin/develop```## Examples```bash# Check workspace status/workspace-status# Check specific workspace/workspace-status /path/to/workspace# Detailed status with file changes/workspace-status --detailed```## Features- Multi-repository detection- Cross-repository dependency analysis- Conflict detection and reporting- Workspace boundary identification- Git state analysis per repository## Integration- Works with all git commands- Integrates with PR workflow- Supports Linear issue tracking- Compatible with branch management---> Converted and distributed by [TomeVault](https://tomevault.io/claim/gullitmiranda) — claim your Tome and manage your conversions.

Frequently asked questions