validate-workspace

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Validate Career Workspace

验证 Career 工作区

Keep career records findable and, when requested, align an existing workspace to the standard physical

career/

homes:

profile/

projects/

brand/

assets/

research/

. Legacy paths can remain operational via mappings until an authorized migration. Use this skill on demand, not as a prerequisite for other skills.

确保职业记录易于查找，并在收到请求时，将现有工作区与标准物理

career/

目录对齐：

profile/

、

projects/

、

brand/

、

assets/

、

research/

。在获得迁移授权之前，旧路径可以通过映射继续使用。仅按需使用此 skill，不要将其作为其他 skill 的前置条件。

Contract

契约

Input: An explicit workspace-validation request or a structural blocker encountered during another task; relevant files/index and existing permissions when available.
Scope: Verify structural paths, links and canonical-record ownership; repair only authorized mappings. Career facts and published content belong to other skills.
Output: One status (
```
valid
```
,
```
repaired
```
,
```
proposed
```
or
```
blocked
```
), checked scope, verified changes or patch, and the resolved path or next question.

输入： 明确的工作区验证请求，或在其他任务中遇到的结构性阻塞；如可用，还需提供相关文件/索引和现有权限。
范围： 验证结构路径、链接和规范记录的归属；仅修复已获授权的映射。职业资料和已发布内容由其他 skill 处理。
输出： 一个状态（
```
valid
```
、
```
repaired
```
、
```
proposed
```
或
```
blocked
```
）、已检查的范围、已验证的更改或补丁，以及已解析的路径或下一个需要确认的问题。

Repair rule

修复规则

A request to check, review or resume is read-only for structure: report the status and the proposed fix, then ask before changing files.
A link to a renamed or moved record: update the link and the index entry; the user's file name and location win.
Rename or move a record to its standard name only when the user explicitly asks to standardize the layout.

对检查、审查或继续执行的结构请求采用只读方式：报告状态和拟议修复方案，然后征得同意后再更改文件。
对于指向已重命名或已移动记录的链接：更新链接和索引条目；以用户指定的文件名和位置为准。
只有当用户明确要求标准化布局时，才能将记录重命名或移动到其标准名称。

Steps

步骤

Choose scope. For a task blocker, check only the failed lookup/link; a working legacy mapping does not trigger migration. For an explicit workspace review, inspect the index and mapped existing records; when the user asks for standardization, also compare physical homes with the standard
```
career/
```
layout. Report inaccessible areas. An uncreated unused home or absent index does not block work from supplied records. Initial workspace creation and source imports belong to
```
setup-career-skills
```
.
Verify the mapping. For a review, run
```
python3 scripts/check_workspace.py <root>
```
from this skill's folder when Python 3 is available (exit 0 usable, 1 errors listed, 2 root missing;
```
--json
```
for structured output); otherwise check by reading. Resolve existing canonical paths and relevant links, identify competing authorities, and separate broken references from usable legacy mappings. For an explicit alignment request, inventory proposed moves, path collisions and affected inbound/outbound links before editing.
Select a repair. For a broken link, prefer a small index/link fix. For user-requested standardization, propose relocation to canonical home names, including link updates, conflicts and history preservation (use a reviewable PR when relevant). Ask about ambiguous ownership. Moving, renaming, merging or deleting requires a specific approved plan.
Apply within scope. Apply a narrow index/link correction only when the user asked for the fix, or when another task is blocked and that task already has write permission; a saved write policy alone is not a request. Otherwise present the patch and ask. Preserve unrelated changes and follow the provider's version/PR workflow. Verify that changed references resolve after the write.
Return a result. Use
```
valid
```
for checked mappings without defects,
```
repaired
```
for a confirmed fix,
```
proposed
```
for a fix awaiting approval/access and
```
blocked
```
when the required authority or files remain unknown. Name the affected paths and any unresolved question. When called from another task, return the resolved locator so the original task can continue; an unresolved blocker may instead require supplied evidence.

选择范围。 对于任务阻塞，仅检查失败的查找或链接；正常工作的旧版映射不会触发迁移。对于明确的工作区审查，检查索引和已有映射记录；当用户要求标准化时，还要将物理目录与标准
```
career/
```
布局进行比较。报告无法访问的区域。未创建但未使用的目录或缺失索引，不会阻止基于用户提供的记录开展工作。初始工作区创建和来源导入由
```
setup-career-skills
```
负责。
验证映射。 进行审查时，如果 Python 3 可用，则从此 skill 的文件夹运行
```
python3 scripts/check_workspace.py <root>
```
（退出码 0 表示可用，1 表示列出了错误，2 表示根目录缺失；
```
--json
```
用于结构化输出）；否则通过读取文件进行检查。解析现有规范路径和相关链接，识别相互冲突的权威来源，并区分断裂引用和可用的旧版映射。对于明确的对齐请求，编辑前先清点拟议移动、路径冲突以及受影响的传入/传出链接。
选择修复方案。 对于断裂链接，优先进行小范围的索引或链接修复。对于用户请求的标准化，提出将记录迁移至规范目录名称的方案，其中包括链接更新、冲突处理和历史保留（在相关情况下使用可审查的 PR）。对于归属不明确的情况，询问用户。移动、重命名、合并或删除记录均需要具体且已获批准的方案。
在范围内应用。 仅当用户要求修复，或另一任务受阻且该任务已有写入权限时，才应用小范围的索引或链接更正；仅保存了写入策略并不构成修复请求。否则应展示补丁并征求同意。保留无关更改，并遵循提供方的版本或 PR 工作流。写入后，验证已更改的引用能够正确解析。
返回结果。 对于未发现缺陷的已检查映射，使用
```
valid
```
；对于已确认并完成的修复，使用
```
repaired
```
；对于等待批准或访问权限的修复，使用
```
proposed
```
；当所需权限或文件仍不明确时，使用
```
blocked
```
。指明受影响的路径和任何未解决的问题。从其他任务调用时，返回已解析的定位信息，使原任务能够继续；未解决的阻塞则可能需要用户提供证据。

Done when

完成标准

The requested scope has been checked; relevant mappings and access limits are explicit.
The status matches observed evidence and actual write results.
Any applied fix is authorized, verified and repeatable without further changes.
Existing custom layouts and unrelated content remain intact.

已检查请求指定的范围，并明确相关映射和访问限制。
状态与观察到的证据和实际写入结果一致。
所有已应用的修复均已获得授权、完成验证，且无需进一步更改即可重复执行。
现有自定义布局和无关内容保持完整。