Community코딩 & 개발github.com

microsoft/hygiene

코드 변경 시 VS Code의 위생 검사(hygiene checks)를 통과하는지 확인할 때 사용합니다. pre-commit 훅, 유니코드 제한, 문자열 따옴표 규칙, 저작권 헤더, 들여쓰기, 포맷팅, ESLint 및 stylelint를 다룹니다. 작업 완료를 선언하기 전에 위생 검사를 실행하세요.

hygiene란 무엇인가요?

이 스킬은 VS Code 저장소에 기여할 때 필수적인 위생 검사(hygiene checks)를 자동화합니다. 개발자가 코드 변경 사항을 제출하기 전에 pre-commit 훅, 유니코드 제한, 문자열 따옴표 규칙, 저작권 헤더, 들여쓰기, 포맷팅, ESLint, stylelint 등 다양한 규칙을 준수하는지 확인합니다. 특히 VS Code의 엄격한 코딩 표준을 따르는 대규모 오픈소스 프로젝트에서 유용하며, 코드 리뷰 과정에서 발생할 수 있는 사소한 오류를 사전에 방지합니다. 명령줄에서 `npm run hygiene` 또는 유사한 스크립트를 실행하여 검사를 수행할 수 있으며, 결과는 터미널에 출력됩니다. 이 스킬은 CI/CD 파이프라인과 통합되거나 로컬 개발 환경에서 사전 커밋 훅으로 사용될 수 있어, 일관된 코드 품질을 유지하는 데 도움을 줍니다.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/microsoft/vscode/tree/main/skills/hygiene

Installed? Explore more 코딩 & 개발 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

hygiene은(는) 무엇을 하나요?

코드 변경 시 VS Code의 위생 검사(hygiene checks)를 통과하는지 확인할 때 사용합니다. pre-commit 훅, 유니코드 제한, 문자열 따옴표 규칙, 저작권 헤더, 들여쓰기, 포맷팅, ESLint 및 stylelint를 다룹니다. 작업 완료를 선언하기 전에 위생 검사를 실행하세요.

Individual skills in this repo

This repo contains 10 individual skills — each has its own dedicated page.

microsoft/accessibility

Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.

microsoft/agent-sessions-layout

Agents workbench layout — covers the fixed layout structure, grid configuration, part visibility, editor modal, titlebar, sidebar footer, and implementation requirements. Use when implementing features or fixing issues in the Agents workbench layout.

microsoft/author-contributions

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

microsoft/azure-pipelines

Use when validating Azure DevOps pipeline changes for the VS Code build. Covers queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes without waiting for full CI runs.

microsoft/fix-errors

Guidelines for fixing unhandled errors from the VS Code error telemetry dashboard. Use when investigating error-telemetry issues with stack traces, error messages, and hit/user counts. Covers tracing data flow through call stacks, identifying producers of invalid data vs. consumers that crash, enriching error messages for telemetry diagnosis, and avoiding common anti-patterns like silently swallowing errors.

microsoft/memory-leak-audit

Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.

microsoft/sessions

Agents window architecture — covers the agents-first app, layering, folder structure, chat widget, menus, contributions, entry points, and development guidelines. Use when implementing features or fixing issues in the Agents window.

microsoft/tool-rename-deprecation

Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.

microsoft/update-screenshots

Download screenshot baselines from the latest CI run and commit them. Use when asked to update, accept, or refresh component screenshot baselines from CI, or after the screenshot-test GitHub Action reports differences. This skill should be run as a subagent.

microsoft/validate-ui-scenario

Use when reproducing a UI bug or verifying a fix by driving a real VS Code window end to end and capturing evidence. Writes a scenario file, runs it against a dev build or installed Insiders, and produces a captioned video, per-step screenshots, a Playwright trace, and an HTML report to attach to an issue or pull request.

관련 스킬