「lint」の検索結果

Use when keeping imp's docs and config examples coherent after a change - updating docs/internals/ARCHITECTURE.md / README / docs/GOAL.md / docs/MODELS.md / docs/roadmap.md / imp.conf.example / CHANGELOG / MISSION_JOURNAL, or "is this doc stale", "document this change", "the example config is out of date", "the README says X but the code does Y", "add a roadmap ledger row". Do NOT use for layer/frontmatter/lint questions (docs-layers), structural code audits (codebase-audit), measuring perf or refreshing the perf baseline (benchmark-cuda), or the agent's private memory (MEMORY.md).

日本語の概要は準備中です。原文の説明を表示しています。

Use HTMLHint in .NET repositories that ship static HTML output or standalone frontend templates. Use when a repo needs a focused CLI lint gate for DOM structure, invalid attributes, and basic HTML correctness checks on static pages.

日本語の概要は準備中です。原文の説明を表示しています。

Complete development with structured merge/PR options. Use when ready to merge or submit work.

日本語の概要は準備中です。原文の説明を表示しています。

Scaffolds CI/CD pipeline definitions using GitHub Actions for build, test, lint, and deploy workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Lint, build, test, verify specs, commit, and push — one micro-commit to remote. Validates the working tree, verifies spec alignment, and creates an atomic save point.

日本語の概要は準備中です。原文の説明を表示しています。

Generate a GitHub Actions workflow for Android — JDK + Gradle caching, build, unit + instrumented tests, Android Lint, run the Android pre-flight checks, and (optionally) sign + upload a signed app bundle to a Play track. Use when setting up CI for an Android app.

日本語の概要は準備中です。原文の説明を表示しています。

Health-check the project knowledge base. Looks for contradictions between files, stale claims that newer sources have superseded, orphan files with no inbound cross-references, important concepts mentioned but lacking their own page, missing cross-references, and data gaps. Returns a structured report; does not auto-fix.

日本語の概要は準備中です。原文の説明を表示しています。

Run Claude Code in autonomous iteration loops until task completion — PRD-based feature development, test coverage improvement, lint fixing, documentation generation, dataset creation, or framework migrations. Uses in-session loop mechanism with specialized templates. Triggers on autonomous loop, iterate until done, run until passing, keep going until, ralph, PRD execution.

日本語の概要は準備中です。原文の説明を表示しています。

Create, fetch, validate, or export DESIGN.md design system files in the Google Stitch 9-section format. Fetch reference designs from 68 brands (Linear, Stripe, Vercel, etc.) via getdesign CLI, generate scaffolds from existing CSS custom properties and Tailwind tokens, or validate and export with the Google @google/design.md CLI. Pairs with minoan-frontend-design for implementation. Triggers on "DESIGN.md", "create design system file", "extract design tokens", "codify the design", "getdesign", "make it look like [brand]", "lint design", "validate DESIGN.md", "export design tokens", "export tailwind theme".

日本語の概要は準備中です。原文の説明を表示しています。

Start and maintain a fire using friction, spark, and solar methods. Covers site selection, material grading (tinder/kindling/fuel), fire lay construction (teepee, log cabin, platform), ignition techniques (ferro rod, flint & steel, bow drill), flame nurturing, and Leave No Trace extinguishing. Use when needing warmth, light, or a signal in a wilderness setting, when boiling water for purification, when cooking foraged food, or in an emergency survival situation requiring heat or morale support.

日本語の概要は準備中です。原文の説明を表示しています。

Design and implement multi-stage CI/CD pipelines using GitHub Actions with matrix builds, dependency caching, artifact management, and secret handling. Create workflows that span linting, testing, building, and deployment stages with parallel execution and conditional logic. Use when setting up automated testing and deployment for a new project, migrating from Jenkins or CircleCI to GitHub Actions, implementing matrix builds across platforms, adding build caching, or creating multi-stage pipelines with security scanning and quality gates.

日本語の概要は準備中です。原文の説明を表示しています。

Use when writing, reviewing, or refactoring Rust code. Routes the task to handbook chapters on idioms, lints, errors, testing, generics, and pointers under the edition 2024 and current-stable pins.

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to run AST-based structural search, lint, or rewrite of code when regex is too fragile. Not for remote, credential, publish, deploy, or irreversible changes.

日本語の概要は準備中です。原文の説明を表示しています。

Generate CI/CD pipeline (GitHub Actions / GitLab CI) with linting, static analysis, tests, security. Use when user says "ci", "setup ci", "github actions", "gitlab ci", "pipeline".

日本語の概要は準備中です。原文の説明を表示しています。

Generate CI/CD pipeline (GitHub Actions / GitLab CI) with linting, static analysis, tests, security. Use when user says "ci", "setup ci", "github actions", "gitlab ci", "pipeline".

日本語の概要は準備中です。原文の説明を表示しています。

Build, test, run, lint, format, and manage dependencies for Haskell projects using the hx toolchain CLI. Use whenever working in a Haskell project that has an hx.toml (or when setting one up), or when the user asks to build/test/run/typecheck Haskell code, manage GHC/Cabal versions, or add/remove Hackage dependencies.

日本語の概要は準備中です。原文の説明を表示しています。

kbo-cli 의 작업 브랜치에서 develop 으로 향하는 새 PR 을 만든다. 단순 push+gh pr create 가 아니라, /code-review 로 diff 검토 → biome check (format+lint) → tsc typecheck → bun build → bun test 5단계 검증을 통과시킨 뒤에 PR 을 올린다. PR 제목·본문은 모두 한국어 Angular 컨벤션 (CLAUDE.md 참조). 사용자가 "PR 올려줘", "pull request 만들어줘", "PR 생성해줘", "이거 PR 로 정리해줘", "리뷰 받게 올려줘" 같은 PR 생성 의도를 보이거나, 기능 작업이 끝나서 머지 흐름을 시작하려는 맥락이면 반드시 이 스킬을 쓴다. push 만 하고 끝나는 단순 push 요청과 다르다 — push 직전에 검증을 강제하는 게 핵심이다.

日本語の概要は準備中です。原文の説明を表示しています。

Iteratively review and fix issues on the current branch until the review passes.

日本語の概要は準備中です。原文の説明を表示しています。

Investigate a topic, library, or approach before planning. Combines user context, prior knowledge, and external sources.

日本語の概要は準備中です。原文の説明を表示しています。

Amend the last commit with current changes and/or an updated message.

日本語の概要は準備中です。原文の説明を表示しています。

Stage changes and create a commit with a conventional commit message.

日本語の概要は準備中です。原文の説明を表示しています。

Three-phase code review. Investigates internally, verifies findings, then reports only confirmed issues.

日本語の概要は準備中です。原文の説明を表示しています。

Full autopilot — plan, implement, and polish a task end-to-end.

日本語の概要は準備中です。原文の説明を表示しています。

Fetch and display diffs for various scopes (PR, commit, branch, staged, working tree). Used by other skills that need to analyze changes.

日本語の概要は準備中です。原文の説明を表示しています。