nx-workspace
Explore and Diagnose Nx Workspaces
Nx monorepos hide resolved targets, dependencies, and affected projects behind layered configuration. This skill uses Nx JSON output and command-line filters to produce precise workspace answers.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
Review the Skillstore skill "nx-workspace" from https://skillstore.io/skills/nrwl-nx-workspace.md and its manifest at https://skillstore.io/api/skills/nrwl-nx-workspace/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «nx-workspace». List applications and show which ones provide a build target.
Ожидаемый результат:
Applications: storefront, admin, and api. storefront and admin provide build targets; api exposes serve and test only.
Использование «nx-workspace». What depends on shared-ui?
Ожидаемый результат:
Direct dependents: storefront and admin. No other project has a direct dependency on shared-ui.
Использование «nx-workspace». Why does api:lint fail with missing configuration?
Ожидаемый результат:
The resolved api configuration has build, serve, and test targets, but no lint target. Add or infer lint configuration before running api:lint.
Аудит безопасности
Средний рискAll 47 external-command findings are false positives caused by Markdown backticks and fenced examples, not Ruby or shell command substitution. Both sensitive-file findings are jq `.key` projections, not certificate or private-key access. Semantic review found that `nx sync` and `nx reset` can alter workspace or cache state despite the read-only claim.
Подтверждённые проблемы безопасности (1)
Факторы риска
⚙️ Внешние команды (47)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/nrwl-nx-workspace/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/nrwl-nx-workspace?utm_source=security_passport_badge)Значок HTML
<a href="https://skillstore.io/skills/nrwl-nx-workspace?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/nrwl-nx-workspace/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Встраиваемая карточка
<iframe src="https://skillstore.io/embed/skills/nrwl-nx-workspace.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Академические ссылки (APA · BibTeX · CFF)
Цитата APA
nrwl. (2026). nx-workspace security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/nrwl-nx-workspace/audits/1Цитата BibTeX
@techreport{nrwl-nrwl-nx-workspace-2026,
author = {nrwl},
title = {nx-workspace security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/nrwl-nx-workspace/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nx-workspace security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "nrwl"
date-released: "2026-08-27"
url: "https://skillstore.io/skills/nrwl-nx-workspace/audits/1"
identifiers:
- type: other
value: "skillstore:nrwl-nx-workspace:audit:1"
description: "Skillstore immutable audit report identifier"
Оценка Skillstore
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
Map an unfamiliar monorepo
List applications and libraries, inspect their tags, and trace dependencies before making a change.
Audit target configuration
Compare resolved build, test, and lint targets across projects without relying on partial project files.
Scope continuous integration
Identify affected projects for a branch or commit range and confirm each required target exists.
Попробуйте эти промпты
List every project in this Nx workspace. Group applications and libraries, then note each project with a build target.
Inspect the resolved configuration for [project]. Summarize its root, tags, targets, executors, inputs, and outputs.
Show what [project] depends on and which projects depend on it. Use the Nx project graph and summarize dependency types.
Find projects affected between [base] and [head]. Verify their [target] configuration and explain any missing or inconsistent targets.
Лучшие практики
- Use Nx JSON output for project, target, and graph questions.
- Inspect resolved project configuration instead of relying only on project.json.
- Review repository trust and pending changes before running any state-changing command.
Избегать
- Do not count or parse complex terminal output manually when structured output exists.
- Do not assume every project exposes standard build, test, or lint targets.
- Do not run nx sync or nx reset as read-only diagnostics without explicit approval.
Часто задаваемые вопросы
Does this skill change source files?
Does it require a global Nx installation?
Why inspect resolved project configuration?
Can it find affected projects?
Can it explain project dependencies?
What tools improve structured analysis?
Сведения для разработчиков
Автор
nrwlЛицензия
MIT
Ревизия Skillstore
r1
Примечание о версии
Автор не указал версию.
Ссылка
f6cdb76d1aa56a8781522efba21cd0d656ccc802
Актуальность поддержки
28.08.2026
Использование
1 загрузок · 0 просмотров
Структура файлов