Revalidation 会话验
- 作者仓库星标 0
- 作者仓库 skills-registry
Agent And Skill Revalidation
Use this workflow to keep Codex configuration accurate and coherent with the actual codebase.
Step 1: Structural Validation
Re-read the target agent or skill configuration file in full. Validate every documented fact against the current codebase, including current-session changes:
- File and directory paths exist and match the documentation.
- Referenced tools, reference docs, and linked files exist.
- Named types, classes, dialogs, and namespaces are accurate.
- Documented conventions still match existing code.
Apply objective structural fixes automatically. These corrections do not need approval.
Step 2: Logical Analysis
Analyze the configuration beyond mechanical path checks:
- Responsibilities align with the available tools and reference files.
- Conventions still make sense for the current codebase.
- Sections do not overlap, contradict each other, or duplicate stale guidance.
- Commonly edited areas are covered.
- Self-maintenance rules catch likely side effects.
- Reference files are structured well enough to scale.
Present logical findings one at a time, ordered by importance. For each finding:
- Describe the issue and concrete suggestion.
- Ask the user to approve, reject, or modify the suggestion. Use a concise plain-text question when no structured question tool is available.
- Apply approved changes immediately before moving to the next finding.
Do not batch logical findings. Do not apply logical-analysis changes without user approval.
<!-- tomevault:4.0:skill_md:2026-05-23 -->Source: BitzArt-VS/UI-Tweaks — distributed by TomeVault.
- 流狐分类
- AI 智能
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @tomevault-io · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。Re-read the target agent or skill configuration file in full. Validate every documented fact against the current codebase, including current-session changes: File and directory paths exist and match the documentation. Referenced tools, reference docs, and…
Analyze the configuration beyond mechanical path checks: Responsibilities align with the available tools and reference files. Conventions still make sense for the current codebase.
# Agent And Skill Revalidation
Use this workflow to keep Codex configuration accurate and coherent with the actual codebase.
## Step 1: Structural Validation
Re-read the target agent or skill configuration file in full. Validate every documented fact against the current codebase, including current-session changes:
- File and directory paths exist and match the documentation.
- Referenced tools, reference docs, and linked files exist.
- Named types, classes, dialogs, and namespaces are accurate.
- Documented conventions still match existing code.
Apply objective structural fixes automatically. These corrections do not need approval.
## Step 2: Logical Analysis
Analyze the configuration beyond mechanical path checks:
- Responsibilities align with the available tools and reference files.
- Conventions still make sense for the current codebase.
- Sections do not overlap, contradict each other, or duplicate stale guidance.
- Commonly edited areas are covered.
- Self-maintenance rules catch likely side effects.
- Reference files are structured well enough to scale.
Present logical findings one at a time, ordered by importance. For each finding:
1. Describe the issue and concrete suggestion.
2. Ask the user to approve, reject, or modify the suggestion. Use a concise plain-text question when no structured question tool is available.
3. Apply approved changes immediately before moving to the next finding.
Do not batch logical findings. Do not apply logical-analysis changes without user approval.
---
> Source: [BitzArt-VS/UI-Tweaks](https://github.com/BitzArt-VS/UI-Tweaks) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> Step 1: Structural Validation → Step 2: Logical Analysis
要点 -> Use this workflow to keep Codex configuration accurate and coherent with the actual codebase. · Re-read the target agent or skill configuration file in full. · - File and directory paths exist and match the documentation. · Apply objective structural fixes automatically. · - Responsibilities align with the available tools and reference files. · Present logical findings one at a time, ordered by importance. · 1. Describe the issue and concrete suggestion. · Do not batch logical findings.
文件/命令 -> BitzArt-VS/UI-Tweaks · github.com/BitzArt-VS/UI-Tweaks
内容 SHA-256 -> 84191a7aa85a
方法与流程
适用与边界
原文中的明确线索
BitzArt-VS/UI-Tweaks、github.com/BitzArt-VS/UI-Tweaks