Markuplint

Add, remove, or adjust Markuplint rules for specific files or elements. Analyzes violations, proposes scope-appropriate configuration changes, and confirms with the user.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set up Markuplint in a project from scratch. Detects framework, creates config, runs initial lint, and guides the user through rule adoption with Bulk Suppressions support.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reference knowledge for Markuplint HTML linter. Covers violation interpretation, CLI usage, config patterns, and documentation URLs. Auto-loaded when working with HTML linting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deprecated install path for the v4-to-v5 migration skill. Prefer npx skills add markuplint/markuplint@migrations/v4-v5 — content lives in skills/migrations/v4-v5/SKILL.md.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Maintenance of the nu-validator coverage benchmark: defend the invariants (nu-only = 0, xref audit green), follow up a nu-validator upstream update (submodule bump / Docker image drift), and regression-check after markuplint rule or spec changes. Use when updating the validator submodule, when a bench refresh surfaces new nu-only entries, when excluded-ids entries go stale, or for the periodic health check. Trigger keywords: bench maintain, bench maintenance, nu update, submodule bump, validator update, bench refresh, nu-only regression, stale excluded-ids, image digest.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Enable an existing or newly-added markuplint rule on the nu-validator bench by editing tests/external/bench/config.ts. Covers the flat-rule case (rules: { '<name>': true }) and the severity override case (rules: { '<name>': { severity: 'error' } }) that bench-virtual-rule does not. Use when a rule exists in the registry but the relevant nu fixtures stay nu-only because the rule is not enabled in the bench config, or when a rule's default severity is warning but the spec text it mirrors is a MUST / MUST NOT. Trigger keywords: enable bench rule, bench config flat rule, severity override bench, rule not flagging on bench, warning vs error in bench, escalate severity bench, no-contradictory-aria-prop bench, bench coverage missing rule.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set up the nu-validator benchmark environment — initialise the validator submodule, ensure Docker is running, populate the gitignored raw snapshots via yarn bench:update. Also covers Docker / nu-runner troubleshooting. Use when bench commands fail with "no snapshots found", "Docker daemon not reachable", port 28888 conflicts, or healthcheck timeouts; or when refreshing the bench after a long break. Trigger keywords: bench setup, bench Docker, validator submodule, no snapshots found, Docker daemon not reachable, healthcheck times out, port 28888, yarn bench:update first time, bench install, fresh clone bench.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Triage one nu-only fixture from tests/external/snapshots/diff/nu-only.json by reading the spec, then drive its verdict to match-error, match-clean, or nu-over by either fixing markuplint or recording an excluded-ids.json entry. The core per-fixture operation of the nu-validator coverage benchmark. Use when a bench refresh surfaces new nu-only entries, when checking a coverage-claim ("markuplint misses X" / "over-detects Y") against the bench, or when classifying a specific fixture. Trigger keywords: nu-only, ml-only, coverage gap, bench triage, verdict, match-error, match-clean, nu-over, excluded-ids, declare nu over-detection, claim audit, audit fixture, mark-up valid per spec, spec-cited exclusion.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Mirror a preset virtual rule (selectors under `nodeRules` in preset.html-standard.jsonc and similar) into bench/config.ts so the benchmark exercises it. Use when a new disallowed-element / similar selector lands in a preset and the matching nu fixtures remain stuck at nu-only despite the new rule existing in markuplint. Trigger keywords: virtual rule, nodeRules, disallowed-element, preset html-standard, bench config mirror, rule does not fire on bench, preset rule not exercised.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Sync benchmark cross-reference blocks onto GitHub Issue bodies via `yarn bench:xref`, manage `tests/external/bench/issue-xref.config.ts` mappings, and run the pre-release checklist. Use when adding / removing / updating a primary or secondary mapping, when an issue closes upstream, when the xref CLI's output disagrees with what's on the issue body, or before cutting a release that touches a rule the benchmark covers. Trigger keywords: bench-xref, issue-xref, xref CLI, GitHub issue body, primary mapping, secondary mapping, umbrella block, pre-release checklist, bench-xref-audit workflow, marker version.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Investigate a problem to its root cause and file it as a GitHub Issue with the right labels and an As is / To be / Why / How body backed by primary sources. Use when asked to file, create, or open an issue, or when the `impl` skill hands over a carry-over. Trigger keywords: create issue, file an issue, open an issue, report a bug as an issue.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Documentation policy — JSDoc-first; no code-derivable markdown. Use when writing or reviewing any repository documentation (JSDoc, README, markdown) or deciding where a piece of documentation belongs. Trigger keywords: documentation, JSDoc, README, markdown policy, docs, comment policy.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create and maintain framework parser and spec packages for markuplint — package types, naming, and the architectural constraints that break the build or runtime contracts when violated. Use when adding or modifying any @markuplint/*-parser or @markuplint/*-spec package. Trigger keywords: new parser, template engine parser, framework parser, spec package, ExtendedSpec, ignoreTags, component-scanner.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Git operation rules for this repository — branch guard, commit granularity, package commit order, Conventional Commits message format, and pre-commit checks. Use whenever creating commits or asked to "commit". Trigger keywords: commit, git commit, stage, staging, commit message, conventional commits.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Thoroughly question (grill) the user's plan, design, or decision until a shared understanding is reached — one question at a time, each with a recommended answer. Use when the user wants to firm up a plan or design, and proactively before a non-trivial implementation whose scope, approach, or trade-offs have not yet been agreed in the conversation. Trigger keywords: grill me, refine the plan, firm up the design, align on scope.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implementation orchestrator — takes an agreed plan through implementation, carry-over approval, code review, security review, QA, docs consistency, lint/test, carry-over filing, commit, PR creation, and the post-merge carry-over check. Invoke with `/impl` once a plan has been agreed (e.g. via grill-me or the issue skill).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze or create a GitHub Issue and build a TDD resolution plan. Use when given an Issue URL to work on, or when a problem report needs to be filed as an Issue first. Trigger keywords: issue, GitHub issue, file an issue, fix issue, resolve issue, issue triage.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

List rule test IDs with filtering and stats. Use when checking test ID coverage, finding missing [rule-name-category-NNN] prefixes, or picking the next available ID number. Trigger keywords: test id, test ids, rule test list, missing id prefix, list-rule-test.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Post-merge steps for a pull request of this repository: completion comment for an external author, report to issue authors other than the owner, and closing the issues a v6 merge left open. Invoked by the `pr` and `pr-review` skills after the user says the PR is merged, or by the user as `/merged <n>`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review an external pull request for the owner: check it against the intake conditions of CONTRIBUTING.md (eligible issue, required body sections, no burst of PRs across repositories) and stop there when it fails them; then read the PR and its linked issues, verify the problem is real (against the current spec when it is a spec matter), assess the authors' trustworthiness, run /code-review xhigh on the PR, and report trust / contribution / mergeability / follow-ups. Use when the user asks to review, check, or triage a PR before merging. Trigger keywords: pr review, review PR, triage PR, can I merge.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create and push a pull request — pre-flight checks, base tracking, PR body drafting, conflict detection, and CI watch loop. Use when asked to open, create, or push a PR. Trigger keywords: pull request, PR, open a PR, push branch, gh pr create.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a diff of this repository from a Product Manager (PdM) perspective: documentation consistency (JSDoc placement, comment policy, README accuracy), maintainability, and operational impact of the change. Run by the `impl` and `pr-review` skills in a fresh-context subagent, or when the user explicitly asks for a PdM review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a diff of this repository as a QA engineer: test quality (coverage, test-faking code, swallowed exceptions, conditional logic in tests, hardcoded assertions) and cross-platform/cross-runtime compatibility (Windows, Deno, Bun). Run by the `impl` and `pr-review` skills in a fresh-context subagent, or when the user explicitly asks for a QA review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Release markuplint — branch promotion, version bump (lerna fixed mode), tag push, publish workflow monitoring, npm-state verification, GitHub Release notes, and X post drafting. Use when asked to release, publish, or cut a new version.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.