一键在 Manus 中运行任何 Skill

hazelight-update-audit

星标23

分支9

更新时间2026年7月14日 14:42

Use when comparing recent Hazelight UnrealEngine-Angelscript updates against AngelscriptProject to decide whether plugin changes, OpenSpec proposals, or sync work are needed.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

TDGameStudio

TDGameStudio/AngelscriptProject

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Hazelight Update Audit

Use this skill for read-only review of recent updates in Hazelight/UnrealEngine-Angelscript before deciding whether AngelscriptProject should adopt, defer, or ignore them.

Guardrails

Treat this as audit work. Do not modify source, OpenSpec artifacts, reference docs, or generated files from this skill alone.
The only files this skill may update during audit are its own state and log files, and only when the user explicitly asks to record the result.
Never print GitHub tokens, SSH keys, credential helper contents, or secret environment variables.
Use gh for GitHub access. If auth or repo access fails, report the exact missing prerequisite and stop.
If the user asks to implement a sync, route the work through openspec-work.
Prefer gh api over local clone state for freshness. Use the local clone only as an optional reference source.

Quick Workflow

Verify access:

gh auth status
gh repo view Hazelight/UnrealEngine-Angelscript --json nameWithOwner,visibility,defaultBranchRef,url,updatedAt

Run the helper script:

.\.agents\skills\hazelight-update-audit\scripts\Get-HazelightUpdateAudit.ps1 -Count 20

This is a recent-window preview only.

For older windows, page through commits:

.\.agents\skills\hazelight-update-audit\scripts\Get-HazelightUpdateAudit.ps1 -Count 20 -Page 2

To resume from the last recorded audit checkpoint, run without -BaseSha; the script reads references/audit-state.json when present.
For a complete Angelscript-related range, use path-scoped pagination:
```
.\.agents\skills\hazelight-update-audit\scripts\Get-HazelightUpdateAudit.ps1 `
    -CompleteRange `
    -BaseSha <base> `
    -HeadSha <head> `
    -Json
```
Complete-range mode does not use the repository-wide Unreal compare endpoint, which is subject to the GitHub 10,000-commit limit. It walks the configured Angelscript, extension, UHT, and example paths, deduplicates commits, and fetches each commit's changed files directly.

For a small known base range without the complete path audit, use compare mode:

.\.agents\skills\hazelight-update-audit\scripts\Get-HazelightUpdateAudit.ps1 -BaseSha <base> -HeadSha <head> -Json

After finishing a human-reviewed complete audit, record the checkpoint only when requested:

.\.agents\skills\hazelight-update-audit\scripts\Get-HazelightUpdateAudit.ps1 -CompleteRange -BaseSha <base> -HeadSha <head> -UpdateState

Record the human-readable audit result in references/audit-log.md when the user wants the review to be reusable.
Inspect the equivalent local files before recommending adoption. Path names alone are not enough.
Produce a short report with commit range, changed files by subsystem, authors, UE-following signals, classification, and next action.

Audit Records

Use two files with separate purposes:

references/audit-state.json: machine-readable checkpoint. This is the resume cursor.
references/audit-log.md: human-readable audit history. This records what was reviewed and why each item was classified.

The checkpoint file is intentionally small and committed with the skill so the next audit can continue from the last reviewed upstream point. Track:

lastReviewedHeadSha: upstream commit fully reviewed by humans.
lastReviewedAt: UTC timestamp when the checkpoint was recorded.
lastAuditBaseSha and lastAuditHeadSha: most recent compared range.
lastAuthors: commit authors seen in the last audit range.
lastUnrealEngineFollowSignals: commits that look like UE version/release merges or Epic release tracking.
notes: short human-maintained context for deferred sync decisions.

The log file should record:

audit date, upstream range, HEAD, and checkpoint status.
how many commits were listed versus deeply patch-reviewed.
authors and UE-following signals.
Adopt now, Already absorbed, Needs OpenSpec, Reference only, and Out of scope sections.

Do not update either file just because the script ran. Update them only after the audit result has been reviewed and the user wants it recorded.

Classification

Use these labels consistently:

Adopt now: small, local, low-risk fixes with an equivalent local path, such as binding const correctness, missing includes, or commandlet/headless guards.
Needs OpenSpec: module boundaries, public APIs, build structure, StaticJIT behavior, AngelScript library extraction, settings, replication semantics, or behavior visible to scripts/Blueprints.
Reference only: Hazelight engine-fork behavior, changes already solved differently here, or code useful only as design input.
Out of scope: GAS plugin work, Hazelight sample projects, external VSCode extensions, or non-Angelscript plugin content unless the user explicitly expands scope.

Flag UE-following commits separately. These are often not direct plugin feature work and may represent upstream engine refreshes:

Messages containing Merge remote-tracking branch 'epicgames/.
Messages containing release, UE, Unreal Engine, or version patterns such as 5.7.2.
Large compare ranges dominated by Engine/Source/* outside plugin paths.

Path Mapping

Map upstream paths to local areas before judging relevance:

Hazelight path	Local area
`Engine/Plugins/Angelscript/Source/AngelscriptCode/Private/Binds/*`	`Plugins/Angelscript/Source/AngelscriptRuntime/Binds/*`
`Engine/Plugins/Angelscript/Source/AngelscriptCode/Private/ClassGenerator/*`	`Plugins/Angelscript/Source/AngelscriptRuntime/ClassGenerator/*`
`Engine/Plugins/Angelscript/Source/AngelscriptCode/Private/StaticJIT/*`	`Plugins/Angelscript/Source/AngelscriptRuntime/StaticJIT/*`
`Engine/Plugins/Angelscript/Source/AngelscriptCode/Private/Testing/*`	`Plugins/Angelscript/Source/AngelscriptRuntime/Testing/` or `Plugins/Angelscript/Source/AngelscriptTest/`
`Engine/Plugins/Angelscript/Source/AngelscriptCode/Public/*`	`Plugins/Angelscript/Source/AngelscriptRuntime/Public/*` or runtime public headers
`Engine/Plugins/Angelscript/Source/AngelscriptEditor/*`	`Plugins/Angelscript/Source/AngelscriptEditor/*`
`Engine/Plugins/AngelscriptGAS/*`	`Out of scope` by default
`Script-Examples/*`	`Script/Examples/*` or functional-test migration references

Report Shape

Keep reports compact:

Repo, branch, audited range, and audit time.
Local Hazelight clone status if available.
Previous checkpoint and whether the audit resumed from it.
Recent commits and changed files grouped by subsystem.
Commit authors and UE-following signals.
Recommended action for each candidate sync item.
OpenSpec change suggestions when the item is architectural or behavior-affecting.

同仓库更多 Skills

同仓库

tiddlywiki-wikitext

TDGameStudio/AngelscriptProject

Use when creating, editing, converting, or reviewing TiddlyWiki 5/TW5 tiddlers, TiddlyWiki WikiText, filters, widgets, transclusion, macros, procedures, tables, links, code blocks, or TiddlyWiki notes. Use official TiddlyWiki 5 syntax, not MediaWiki wikitext.

2026-07-1423

angelscript-test-guide

TDGameStudio/AngelscriptProject

Use when implementing, extending, or refactoring AngelscriptProject C++ automation tests, especially CQTest, HotReload, Bindings, inline AngelScript fixtures, TEST_CLASS_WITH_FLAGS, TEST_METHOD, ASTEST_AS, FScopedAngelscriptModule, matcher assertions, test helpers, or validation commands.

2026-07-0123

openspec-work

TDGameStudio/AngelscriptProject

Use to explore, think through, start, continue, propose, record, plan, apply, implement, or archive an OpenSpec change in AngelscriptProject, including /opsx:work, /opsx:explore, /opsx:propose, /opsx:apply, /opsx:archive, and the /openspec equivalents. Supports explore/think-only sessions, record-only proposals (no immediate implementation), record-while-implementing, and closing/archiving — all in a single flow.

2026-06-1823

openspec-work

TDGameStudio/AngelscriptProject

2026-06-0323

name	hazelight-update-audit
description	Use when comparing recent Hazelight UnrealEngine-Angelscript updates against AngelscriptProject to decide whether plugin changes, OpenSpec proposals, or sync work are needed.

Hazelight Update Audit

Use this skill for read-only review of recent updates in Hazelight/UnrealEngine-Angelscript before deciding whether AngelscriptProject should adopt, defer, or ignore them.

Guardrails

Treat this as audit work. Do not modify source, OpenSpec artifacts, reference docs, or generated files from this skill alone.
The only files this skill may update during audit are its own state and log files, and only when the user explicitly asks to record the result.
Never print GitHub tokens, SSH keys, credential helper contents, or secret environment variables.
Use gh for GitHub access. If auth or repo access fails, report the exact missing prerequisite and stop.
If the user asks to implement a sync, route the work through openspec-work.
Prefer gh api over local clone state for freshness. Use the local clone only as an optional reference source.

Quick Workflow

Verify access:

gh auth status
gh repo view Hazelight/UnrealEngine-Angelscript --json nameWithOwner,visibility,defaultBranchRef,url,updatedAt

Run the helper script:

.\.agents\skills\hazelight-update-audit\scripts\Get-HazelightUpdateAudit.ps1 -Count 20

This is a recent-window preview only.

For older windows, page through commits:

.\.agents\skills\hazelight-update-audit\scripts\Get-HazelightUpdateAudit.ps1 -Count 20 -Page 2

To resume from the last recorded audit checkpoint, run without -BaseSha; the script reads references/audit-state.json when present.
For a complete Angelscript-related range, use path-scoped pagination:
```
.\.agents\skills\hazelight-update-audit\scripts\Get-HazelightUpdateAudit.ps1 `
    -CompleteRange `
    -BaseSha <base> `
    -HeadSha <head> `
    -Json
```
Complete-range mode does not use the repository-wide Unreal compare endpoint, which is subject to the GitHub 10,000-commit limit. It walks the configured Angelscript, extension, UHT, and example paths, deduplicates commits, and fetches each commit's changed files directly.

For a small known base range without the complete path audit, use compare mode:

.\.agents\skills\hazelight-update-audit\scripts\Get-HazelightUpdateAudit.ps1 -BaseSha <base> -HeadSha <head> -Json

After finishing a human-reviewed complete audit, record the checkpoint only when requested:

.\.agents\skills\hazelight-update-audit\scripts\Get-HazelightUpdateAudit.ps1 -CompleteRange -BaseSha <base> -HeadSha <head> -UpdateState

Record the human-readable audit result in references/audit-log.md when the user wants the review to be reusable.
Inspect the equivalent local files before recommending adoption. Path names alone are not enough.
Produce a short report with commit range, changed files by subsystem, authors, UE-following signals, classification, and next action.

Audit Records

Use two files with separate purposes:

references/audit-state.json: machine-readable checkpoint. This is the resume cursor.
references/audit-log.md: human-readable audit history. This records what was reviewed and why each item was classified.

The checkpoint file is intentionally small and committed with the skill so the next audit can continue from the last reviewed upstream point. Track:

lastReviewedHeadSha: upstream commit fully reviewed by humans.
lastReviewedAt: UTC timestamp when the checkpoint was recorded.
lastAuditBaseSha and lastAuditHeadSha: most recent compared range.
lastAuthors: commit authors seen in the last audit range.
lastUnrealEngineFollowSignals: commits that look like UE version/release merges or Epic release tracking.
notes: short human-maintained context for deferred sync decisions.

The log file should record:

audit date, upstream range, HEAD, and checkpoint status.
how many commits were listed versus deeply patch-reviewed.
authors and UE-following signals.
Adopt now, Already absorbed, Needs OpenSpec, Reference only, and Out of scope sections.

Do not update either file just because the script ran. Update them only after the audit result has been reviewed and the user wants it recorded.

Classification

Use these labels consistently:

Adopt now: small, local, low-risk fixes with an equivalent local path, such as binding const correctness, missing includes, or commandlet/headless guards.
Needs OpenSpec: module boundaries, public APIs, build structure, StaticJIT behavior, AngelScript library extraction, settings, replication semantics, or behavior visible to scripts/Blueprints.
Reference only: Hazelight engine-fork behavior, changes already solved differently here, or code useful only as design input.
Out of scope: GAS plugin work, Hazelight sample projects, external VSCode extensions, or non-Angelscript plugin content unless the user explicitly expands scope.

Flag UE-following commits separately. These are often not direct plugin feature work and may represent upstream engine refreshes:

Messages containing Merge remote-tracking branch 'epicgames/.
Messages containing release, UE, Unreal Engine, or version patterns such as 5.7.2.
Large compare ranges dominated by Engine/Source/* outside plugin paths.

Path Mapping

Map upstream paths to local areas before judging relevance:

Hazelight path	Local area
`Engine/Plugins/Angelscript/Source/AngelscriptCode/Private/Binds/*`	`Plugins/Angelscript/Source/AngelscriptRuntime/Binds/*`
`Engine/Plugins/Angelscript/Source/AngelscriptCode/Private/ClassGenerator/*`	`Plugins/Angelscript/Source/AngelscriptRuntime/ClassGenerator/*`
`Engine/Plugins/Angelscript/Source/AngelscriptCode/Private/StaticJIT/*`	`Plugins/Angelscript/Source/AngelscriptRuntime/StaticJIT/*`
`Engine/Plugins/Angelscript/Source/AngelscriptCode/Private/Testing/*`	`Plugins/Angelscript/Source/AngelscriptRuntime/Testing/` or `Plugins/Angelscript/Source/AngelscriptTest/`
`Engine/Plugins/Angelscript/Source/AngelscriptCode/Public/*`	`Plugins/Angelscript/Source/AngelscriptRuntime/Public/*` or runtime public headers
`Engine/Plugins/Angelscript/Source/AngelscriptEditor/*`	`Plugins/Angelscript/Source/AngelscriptEditor/*`
`Engine/Plugins/AngelscriptGAS/*`	`Out of scope` by default
`Script-Examples/*`	`Script/Examples/*` or functional-test migration references

Report Shape

Keep reports compact:

Repo, branch, audited range, and audit time.
Local Hazelight clone status if available.
Previous checkpoint and whether the audit resumed from it.
Recent commits and changed files grouped by subsystem.
Commit authors and UE-following signals.
Recommended action for each candidate sync item.
OpenSpec change suggestions when the item is architectural or behavior-affecting.