90건 · 관련도순
Run the project's full verification gate: every check the project defines as a pass/fail condition, built from its CI config, check scripts, and configured tools, or from a formatter-linter-test baseline when it declares none. Use when the user asks to "run checks", "run the verification gate", "run lint and tests", "run the test suite", "check that this passes", "does this pass CI", or "run the project's checks".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convert long text into Slack-optimized format with emojis, bullets, code blocks, and threading suggestions
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate configuration files for applications, services, and infrastructure. Use when: (1) Setting up new projects (package.json, requirements.txt, tsconfig.json), (2) Creating Docker or Kubernetes configurations, (3) Configuring CI/CD pipelines (GitHub Actions, GitLab CI, CircleCI), (4) Setting up web servers (Nginx, Apache), (5) Defining infrastructure as code (Terraform, CloudFormation), (6) Generating linter/formatter configs (ESLint, Prettier, Black). Provides templates and custom-generated configs for diverse tech stacks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
You are an expert in Biome, the Rust-based toolchain that replaces ESLint and Prettier with a single, fast tool. You help developers configure linting, formatting, and import sorting for JavaScript, TypeScript, JSX, JSON, and CSS — achieving 100x faster execution than ESLint+Prettier with zero configuration, unified diagnostics, and IDE integration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure ATS-friendly formatting and create clean scannable layouts
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect, triage, de-duplicate, and raise compiler bug reports when an agent encounters a likely compiler defect during implementation, review, testing, or issue work. Use when a task surfaces an ICE, panic, wrong accept/reject behavior, miscompile, lowering/emission bug, diagnostic bug, formatter/LSP/frontend drift, or other likely compiler/tooling defect; pause current work, minimize the repro, decide whether the bug blocks the task or has a valid workaround, check whether it is already reported, and then use create-github-issue to raise the bug.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill whenever writing or editing Rust `//`, `///`, or `//!` comments in Biome, including comments added incidentally and end-user rustdoc inside lint/assist declarations. For lint/assist rustdoc, also load lint-rule-development for content requirements. Do not use for formatter handling of comments in user code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Format Haskell source files: *.hs, *.lhs, and *.hsig, with the project's configured formatter: fourmolu, ormolu, or stylish-haskell. Use before compiling, after source edits, and when applying project style.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Biome is a high-performance Rust-based toolchain for JavaScript, TypeScript, JSX, JSON, CSS, and GraphQL that unifies formatting and linting in a single tool. With 97% Prettier compatibility and over 450 lint rules, Biome replaces ESLint and Prettier with dramatically faster execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use Biome in .NET repositories that ship Node-based frontend assets and want a fast combined formatter-linter-import organizer for JavaScript, TypeScript, CSS, JSON, GraphQL, or HTML. Use when a repo prefers a modern all-in-one CLI over a larger ESLint plus Prettier style stack.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply the team style guide to source files - naming conventions, comment style, and file organization. Use when the user asks to align code with the style guide or clean up naming.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Format technical engineering reports using company layout rules. Use when asked to clean up, standardize, or prepare inspection reports and equipment manuals. Do not use for legal contracts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Format technical PDF reports using company layout rules. Use when asked to clean up, standardize, or prepare inspection reports, equipment manuals, or engineering reports. Do not use for legal contracts or general writing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Biome v2 unified linter, formatter, and import organizer — single Rust-powered tool replacing ESLint + Prettier with 97% Prettier compatibility and 20x faster performance
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MemoryPack high-performance binary serialization for Unity including custom formatters, versioning, and performance patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection. Use for research storytelling, contribution framing, paper comparison, figure planning, or research retrospectives. Not an acceptance predictor or a routine grammar/citation formatter.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run linters and formatters to fix code style issues. Use when cleaning up style violations, formatting code, or after implementation to ensure code meets project standards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when splitting a domain Skill into Phase-Aware File Structure (SKILL.md / design.md / constraints.md). Defines the splitting criteria, procedures, sync procedures, and validation rules. Invoked by /skill-format command or manually when restructuring domain Skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply code formatting rules after file edits in the source directory. Use when asked to format code or after making changes to source files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Quality] Use when a workflow step or the user asks for linters, formatters, type checks and static analysis in pre-commit and CI gates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by create-issue, create-issue-from-issue-number, and update-issue. It formats an implementation-ready GitHub Issue body, runs the pre-posting checklist, executes `gh issue create` or `gh issue edit`, and optionally posts a 確認事項 follow-up comment. Invoke this skill ONLY from one of the three parent skills via the Skill tool, after the parent has completed analysis. If a user asks to 'format an issue body' or similar, route them to the appropriate parent skill (/create-issue, /create-issue-from-issue-number, or /update-issue) rather than invoking this one directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by answer-issue-questions and breakdown-issues. It formats a scope GitHub Issue body (label cc-triage-scope, used before code analysis), runs the pre-posting checklist, and executes `gh issue create`. Invoke this skill ONLY from one of the parent skills via the Skill tool, after the parent has finalized the task breakdown. If a user asks to 'create a scope issue' or similar, route them to the appropriate parent skill (/breakdown-issues for fresh breakdowns, /answer-issue-questions for derived sub-tasks) rather than invoking this one directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
将Markdown文章转换为美化的HTML格式，适配微信公众号发布。应用专业CSS样式、代码高亮、优化排版。当用户说"美化这篇文章"、"转换为HTML"、"优化公众号格式"、"生成公众号HTML"时使用。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.