agentsclimarketplace

Typescript monorepo

Skill unoplat/unoplat-code-confluence/unoplat-code-confluence-query-engine/src/unoplat_code_confluence_query_engine/skills/typescript-monorepo

Always keep your codebases ready for Agents. Improve any coding workflow by atleast 2x by maintaing a live, pluggable context layer per repo that creates and maintains Agents.md

Install
npx -y skills add unoplat/unoplat-code-confluence --skill typescript-monorepo

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Guidance for TypeScript monorepos with mixed package managers. Use when codebase has inherited package manager and a workspace root.

SKILL.md

3.1 KB, as published. Nobody here has run it

TypeScript Monorepo Workflow Guidance

Install Commands

  • Workspace-scoped install runs from workspace root, not leaf
  • bun: bun install at workspace root
  • pnpm: pnpm install at workspace root
  • npm: npm ci at workspace root
  • working_directory = workspace root (repo-relative)

Workspace Root Discovery

  • If workspace_root is present, use it as the direct hint for workspace-owned commands
  • If workspace_root is missing but provenance is inherited, walk upward from codebase_path to find the nearest owning workspace root
  • Inspect parent directories one level at a time with absolute paths using get_directory_tree and read_file_content
  • Stop when you find the nearest workspace-owned signals such as pnpm-workspace.yaml, a root package.json with workspaces, a lockfile, turbo.json, or nx.json
  • Do not assume the leaf owns install/build commands just because the exact workspace root was not precomputed

Build Commands

  • Turborepo: turbo run build or bun run build at workspace root
  • Individual: bun run build --filter <package> from workspace root
  • Check turbo.json or nx.json for build pipeline configuration
  • working_directory = workspace root

Test/Lint/TypeCheck Commands

  • Usually leaf-specific: run from codebase root (omit working_directory)
  • Some monorepos configure workspace-level lint/test via turbo.json/nx.json
  • Inspect the leaf's package.json scripts section for available commands

Working Directory Rules

  • working_directory = workspace root for install/build commands
  • working_directory = omit (None) for leaf-local test/lint/type_check
  • working_directory = "." when command must run from repository root
  • If both workspace-level and leaf-level commands exist for same stage, emit both with distinct working_directory

Config File Path Rules

  • config_file must always be repository-root-relative
  • Never use absolute paths in config_file
  • Never use codebase-relative .. segments in config_file
  • For workspace-owned configs above the leaf, emit the full repository-root path, for example:
    • infra/services/turbo.json
    • infra/services/pnpm-workspace.yaml

Upward Discovery Example

  • Given codebase_path = /opt/unoplat/repositories/acme/infra/services/apps/api and inherited provenance with no workspace_root
  • Inspect /opt/unoplat/repositories/acme/infra/services/apps/api, then /opt/unoplat/repositories/acme/infra/services/apps, then /opt/unoplat/repositories/acme/infra/services
  • If /opt/unoplat/repositories/acme/infra/services/pnpm-workspace.yaml exists, use repo-relative infra/services as the workspace root
  • Then emit workspace-owned commands like install/build with working_directory = "infra/services"

Package Manager Inheritance

  • Leaf inherits manager from nearest workspace aggregator
  • Commands use the inherited manager's CLI (bun, pnpm, npm, yarn)
  • Lock files live at workspace root, not leaf
  • If leaf has its own local manager, provenance=local and no workspace root

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.