Agent Skills
› ccch1mneyyy/dsh-Go
› audit
audit
GitHub针对Go仓库或子系统进行安全、正确性及可维护性审计。通过追踪运行时路径,检查入口点、依赖漏洞及信任边界,识别并报告风险,提供修复建议或仅输出发现结果。
Trigger Scenarios
用户发起 /audit 命令
请求对代码库进行安全或质量审查
Install
npx skills add ccch1mneyyy/dsh-Go --skill audit -g -y
SKILL.md
Frontmatter
{
"name": "audit",
"description": "Audit the ccch1mneyyy\/dsh-Go repository or a broad subsystem for security, correctness, and maintainability risks. Use for audit requests or \/audit; use review for a specific change and vuln-check for a security-only assessment."
}
Establish the audit scope, then trace the relevant runtime paths. For a findings-only request, leave code unchanged; carry out fixes when the user has requested them.
- Identify entry points, state owners, external inputs, and teardown paths within the requested scope.
- Follow inputs through validation and consumers. In this app, inspect applicable host connections (local engine, SSH, relay), session APIs, bridge routes, plugin capabilities, file access, permission flows, and long-session resource bounds. Prioritize paths whose failure can lose state, cross a trust boundary, or leave the terminal unusable. Check dependencies and lockfiles for known vulnerabilities against advisory data.
- Confirm suspected defects against callers, existing guards, and focused regressions. Check exports, registries, and supported compatibility paths before declaring code dead. Explain a simplification in terms of current requirements and the behavior it preserves.
- Report confirmed findings by severity with location, trigger, impact, and a concrete remedy. Keep unverified leads separate. For a cross-layer failure, a short input → boundary → effect trace may be enough to explain it.
- State the areas examined, checks actually run, and material gaps. No findings means none found in that scope, not proof that the whole project is safe. An audit can finish without findings or a forced list of healthy areas.
Version History
- e0c9670 Current 2026-11-16 01:36


