agentleFS
AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/audit-assistant/SKILL.md

audit

Skill4 starsChanged 29 days agoMITView on GitHub

[UDS] Diagnose UDS installation health and submit structured feedback upstream. Use when: .standards/ looks broken or out of sync, verifying manifest integrity, reporting friction with an existing UDS standard. Not for: auditing your own application code quality — use /metrics or /code-review; dependency and secret scanning — use /scan. Keywords: UDS audit, health check, manifest integrity, standards feedback, friction, 安裝健康, 標準稽核, 回饋.

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use delight, teach-impeccable and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • HK-hubSkill

    delight

    Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. Use when the user asks to add polish, personality, animations, micro-interactions, delight, or make an interface feel fun or memorable.

    Also in 32 projects that use this

  • HK-hubSkill

    teach-impeccable

    One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.

    Also in 19 projects that use this

  • zwy123zwySkill

    normalize

    将用户随意输入的提示词规范化为结构清晰、便于大模型执行的标准化提示词。适用于需要整理、统一提示词格式时调用。

    Also in 19 projects that use this

  • SkillPilotCHSkill

    level-up

    Eine Automatisierung pro Woche finden, scopen, shippen. Output landet als proposed-Eintrag in cadence.md mit konkreten Implementations-Schritten.

    Also in 12 projects that use this

  • ww-w-aiSkill

    pm-discovery

    PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.

    Also in 3 projects that use this

  • +7 more from HK-hub

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 175 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run health check on UDS installation.

    line 57
  2. Very specific:

    When suggested by other skills (e.g., /checkin, /commit, /code-review, /sdd), /audit can be invoked to:

    line 124

“Common” is measured: kept by at least 6 in 10 of the 175 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audit Assistant | 審計助手

Language: English | 繁體中文

Version: 1.0.0 Last Updated: 2026-03-04

Diagnose UDS installation health, detect development patterns worth standardizing, identify friction with existing standards, and submit structured feedback to the UDS repository.

診斷 UDS 安裝健康狀態、偵測值得規範化的開發模式、識別與現有標準的摩擦點,並向 UDS 儲存庫提交結構化回饋。

Workflow | 工作流程

DIAGNOSE ──► ANALYZE ──► REPORT
診斷健康      分析模式      回報回饋

Phase 1: DIAGNOSE | 診斷

Run health check on UDS installation.

執行 UDS 安裝健康檢查。

CheckDescription檢查項目
.standards/ existsVerify directory and files驗證目錄與檔案
manifest.json validParse and validate manifest解析驗證 manifest
File integrityCompare hashes against manifest比對雜湊與 manifest
AI config referencesVerify AI config files reference .standards/驗證 AI 設定檔引用

Phase 2: ANALYZE | 分析

Detect patterns and friction points.

偵測模式與摩擦點。

AnalysisMethod分析方法
Directory patternsScan for known standard categories掃描已知標準類別
Commit patternsAnalyze recent 100 commits for recurring topics分析近 100 筆 commit
Modified standardsCompare file hashes (diff-based)比對檔案雜湊
Unused standardsCheck AI config references檢查 AI 設定引用
Orphaned filesFind untracked files in .standards/找出未追蹤檔案

Phase 3: REPORT | 回報

Submit findings as structured GitHub issue.

將發現以結構化 GitHub issue 提交。

MethodCondition方法
gh issue creategh CLI installedgh CLI 已安裝
Browser deeplinkFallback to pre-filled URL退回至預填 URL
Clipboard copyLast resort最終手段複製至剪貼簿

Usage | 使用方式

# Full audit (all layers)
uds audit

# Health check only
uds audit --health

# Pattern detection only
uds audit --patterns

# Friction detection only
uds audit --friction

# JSON output
uds audit --format json

# Summary only (for scripts)
uds audit --quiet

# Submit feedback interactively
uds audit --report

# Preview report without submitting
uds audit --report --dry-run

Integration with Other Skills | 與其他技能的整合

When suggested by other skills (e.g., /checkin, /commit, /code-review, /sdd), /audit can be invoked to:

當被其他技能建議時,/audit 可根據情境執行針對性的檢查:

ContextRecommended Command情境
After /checkin failure/audit --healthcheckin 失敗後診斷
After /commit/audit --report提交後回報發現
After /code-review finds friction/audit --friction審查發現摩擦時
After /sdd spec creation/audit --patterns規格建立後檢查覆蓋率

Next Steps | 後續步驟

After running audit:

FindingAction建議動作
Health ERROR ⭐ Recommended / 推薦Run uds init or uds check --restore執行修復指令
Pattern detectedConsider requesting new standard via --report考慮透過 --report 請求新標準
Modified standardReview if standard needs more flexibility檢視標準是否需要更多彈性
Unused standardConsider removing with uds uninstall考慮移除未使用標準

Related Standards | 相關規範

  • checkin-standards — Code check-in requirements
  • testing-standards — Testing requirements

Version History | 版本歷史

VersionDateChanges
1.0.02026-03-04Initial release — three-layer audit system

License

CC BY 4.0 — See LICENSE for details.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.