workspace

Maps workspace topology, dependencies, API contracts, shared types, and key files across repositories.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/lciacci/tessera --skill workspace-lciacci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace
Source: https://github.com/lciacci/tessera/tree/main/skills/workspace
Command: npx skills add https://github.com/lciacci/tessera --skill workspace-lciacci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents cross-repository and monorepo development from becoming fragmented by mapping workspace structure, dependencies, shared types, API contracts, and key implementation files.

Core Features & Use Cases

  • Workspace Topology Analysis: Classify monorepos, multi-repo workspaces, hybrid environments, and polyglot projects while identifying modules, entry points, and technology stacks.
  • Dependency and Contract Tracking: Extract relationships from imports, API calls, OpenAPI, GraphQL, protobuf, TypeScript, Pydantic, and other contract sources.
  • Freshness and Change Impact Guidance: Maintain topology, contract, dependency, key-file, and capability artifacts; detect stale contracts and identify downstream effects of cross-module changes.
  • Use Case: When changing a backend endpoint in a monorepo, use this Skill to identify affected frontend clients, shared types, database schemas, validation steps, and the recommended implementation order.

Quick Start

Ask the workspace skill to analyze the current repository or workspace, generate its context artifacts, and report any contract inconsistencies or stale sources.

Frequently Asked Questions about workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track cross-repo changes and prevent API contract mismatches?

To track cross-repo changes, map workspace topology and extract relationships from API calls, OpenAPI, GraphQL, and protobuf. This identifies affected downstream clients and shared types to prevent contract mismatches.

What is the best way to analyze dependency graphs in a monorepo?

Analyzing dependency graphs in a monorepo involves classifying the workspace topology and mapping module entry points. This extracts import relationships to detect stale contracts and guide coordinated cross-module changes.

How do I identify affected frontend clients when changing a backend endpoint?

To identify affected frontend clients after a backend endpoint change, perform a workspace analysis. This monitors contract sources and shared types to calculate the downstream impact and recommend implementation order.

Can I use workspace analysis for polyglot systems and hybrid repositories?

Yes, workspace analysis supports polyglot systems, hybrid workspaces, and multi-repository projects. It classifies diverse technology stacks and maps dependencies to maintain shared type freshness across environments.

How do I check if API contracts and shared types are stale in my repository?

To check for stale API contracts and shared types, generate workspace context artifacts and run freshness checks. This monitors contract sources like Pydantic and TypeScript to identify outdated dependencies.