fleetshift
Official@fleetshift
fleetshift provides Nx monorepo skills for workspace exploration, CI self-healing, package linking, code generation, and repository import.
Agent Skills by fleetshift
Showing 7 vetted skills indexed across 1 GitHub repositories.
nx-workspace
Inspect Nx workspace projects, targets, and dependency graphs using nx CLI commands.
monitor-ci
Monitor Nx Cloud CI pipelines and orchestrate self-healing fix workflows.
link-workspace-packages
Link workspace packages in monorepos using npm, yarn, pnpm, or bun workspace commands.
nx-plugins
Discover and install Nx plugins to add framework support to a workspace.
nx-import
Import repositories into an Nx workspace while preserving git history and fixing configuration issues.
nx-run-tasks
Runs build, test, lint, and other tasks in an Nx workspace.
nx-generate
Scaffold applications and libraries in Nx monorepos using workspace generators.
Frequently Asked Questions About fleetshift
FAQPage SchemaWhat tasks can I accomplish with fleetshift's Nx skills?▼
You can explore workspace projects and targets, run build/test/lint/serve tasks, scaffold apps and libraries with nx generators, discover and install Nx plugins, import external repositories into a monorepo, link workspace packages, and monitor Nx Cloud CI with self-healing fixes.
Who should use these Nx workspace skills?▼
Engineers working in Nx monorepos who need to debug task failures, wire up sibling package dependencies, adopt Nx across multiple repositories, or track CI status on a branch. They suit developers managing npm, yarn, pnpm, or bun workspaces with @org/* scoped packages.
How does the monitor-ci skill work in practice?▼
Invoke it with phrases like 'monitor ci' or 'watch ci for this branch'. It accepts arguments for max cycles, timeout minutes, verbosity level, branch, auto-fix behavior, and local verify attempts, integrating with Nx Cloud self-healing rather than native gh or glab providers.
When should I use link-workspace-packages instead of editing config files?▼
Use it when you create new packages, import from a sibling package, or hit resolution errors like 'cannot find module', 'failed to resolve import', or TS2307. It uses the package manager's native workspace commands instead of patching tsconfig paths or manual package.json edits.
What are the prerequisites for using these skills?▼
You need an existing Nx workspace (or repositories to import via nx import), a supported package manager (npm, yarn, pnpm, or bun) for package linking, and Nx Cloud connectivity for the CI monitoring and self-healing capabilities.