원클릭으로
aiws-sdd-audit-style
Audit code style/conventions against a catalogue of engineering conventions (CONV-*). Trigger: style review.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Audit code style/conventions against a catalogue of engineering conventions (CONV-*). Trigger: style review.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | aiws-sdd-audit-style |
| description | Audit code style/conventions against a catalogue of engineering conventions (CONV-*). Trigger: style review. |
| license | Apache-2.0 |
| metadata | {"author":"ai-workspace","version":"1.0"} |
Audit naming, structure, docstrings, logging, error handling, tests and branding against a catalogue of
engineering conventions. Cite findings by control ID. The full CONV-* catalogue is an external
reference (supply your own; not bundled here).
apply_branding: true.A report by category with PASS/FAIL and the file/line. "No invented norms": only cite IDs that exist in the catalogue; new norms go to the catalogue via a separate change.
Produce a prioritized, read-only audit of the workspace's health and coherence (code, docs, integrity, standards) as a dated report. Use periodically or after big changes to surface what to improve. Read-only — it reports and recommends, never fixes.
Configure or re-configure this AI workspace: analyze an existing repo (or set up a new one) and propose a workspace.config.yaml + skill set. Trigger: when the user wants to set up, configure, or re-detect the workspace.
Assess feasibility and security of version bumps/migrations before touching anything. Trigger: when asked to update dependencies, migrate, or resolve version conflicts.
Keep the living docs (project status) current so the AI always has fresh project context. Trigger: after finishing a task or when project state changed.
Implement the tasks in order, keeping the code aligned with the spec and design, checking each off as it lands. Use to execute an agreed plan — if reality diverges from the spec, stop and update the spec first.
Fold a verified change's delta into the stable specs and move its folder to the archive. Use only after verify passes: ADDED requirements are appended, MODIFIED replace, REMOVED delete; then the change is archived with its full history.