通用工程师 开发规范与代码质量
PassAudited by ClawScan on May 8, 2026.
Overview
This is an instruction-only engineering standards skill with purpose-aligned guidance, though users should notice its Technical Lead notification rule and local WLS validation instructions.
This skill appears safe for its stated role as Weline engineering workflow guidance. Before installing, make sure you are comfortable with its rule to notify `@Weline-技术主管` about discovered issues and with running a temporary WLS test instance when validation requires it. The provided SKILL.md excerpt was truncated, so this review is based only on the supplied visible artifact content.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Issue details from the user's development task may be shared with the named Technical Lead in environments that support such notifications.
The skill directs the agent to share discovered issue or risk information with a named Technical Lead/agent. This is disclosed and aligned with its collaboration-hub role, but users should be aware of where task context may be sent.
If any issue, risk, blocker, unclear ownership, or cross-boundary impact is found, notify `@Weline-技术主管` using the required problem report format.
Use in the intended Weline workspace and avoid including secrets, credentials, or unrelated private data in escalation reports.
A local test server may be started during relevant validation work, which can use local resources and open a local port.
The skill may cause local runtime validation by starting a WLS test instance. This is purpose-aligned for engineering validation and bounded by a dedicated port/name plus an explicit stop instruction.
Always start a dedicated WLS test instance with port `9502+` and a unique name such as `ai-test-{timestamp}` when WLS validation is required. Always stop the dedicated WLS test instance after validation.Confirm WLS validation is needed before running it and verify the dedicated test instance is stopped afterward.