← all publishers

markuplint

@markuplint source repo

Report this profile Claim this profile

• 24 skills
• 0 followers
• 7 hours ago last updated

1. ▌
   Pr · markuplint

   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.
   0
   installs
2. ▌
   Markuplint · markuplint

   Reference knowledge for Markuplint HTML linter. Covers violation interpretation, CLI usage, config patterns, and documentation URLs. Auto-loaded when working with HTML linting.
   0
   installs
3. ▌
   Migrate4 5 Legacy Path · markuplint

   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.
   0
   installs
4. ▌
   Doc · markuplint

   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.
   0
   installs
5. ▌
   Git · markuplint

   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.
   0
   installs
6. ▌
   Impl · markuplint

   Implementation orchestrator — takes an agreed plan through implementation, code review, QA, docs consistency, lint/test, commit, and PR creation. Use when the user says "implement it", "go ahead", or "/impl" after a plan has been agreed (e.g. via grill-me or the issue skill).
   0
   installs
7. ▌
   Issue · markuplint

   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.
   0
   installs
8. ▌
   Release · markuplint

   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.
   0
   installs
9. ▌
   Grill Me · markuplint

   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 implementation whenever 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, requirements check.
   0
   installs
10. ▌
    Sponsors · markuplint

    Check current active GitHub Sponsors and sync README/website listings. Used for periodic checks and listing updates.
    0
    installs
11. ▌
    Markuplint Setup · markuplint

    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.
    0
    installs
12. ▌
    Migrate4 5 · markuplint

    Guides you through migrating markuplint configuration from v4 to v5. Detects current versions, reviews the migration guide, interactively confirms breaking changes and new rules with the user, updates config files and tests. For Claude Code.
    0
    installs
13. ▌
    Bench Xref · markuplint

    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.
    0
    installs
14. ▌
    Bench Setup · markuplint

    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.
    0
    installs
15. ▌
    QA Engineer · markuplint

    A skill for performing code reviews and test quality checks as a QA engineer. Improves code coverage, detects test-faking code, catches swallowed exceptions, flags conditional logic in tests, promotes hardcoded assertions, and checks cross-platform/cross-runtime compatibility (Windows, Deno, Bun). Language- and framework-agnostic — works with any repository. Trigger this skill on keywords: code review, test, coverage, QA, quality check, test generation, refactoring. Always use this skill when the user requests a PR review or test improvement.
    0
    installs
16. ▌
    Verify Docs · markuplint

    Verify documentation claims (README, JSDoc) in spec-heavy packages — @markuplint/types (attribute value types; WHATWG/W3C/RFC/CSS/SVG grammars) and @markuplint/ml-spec (HTML/WAI-ARIA algorithms, spec resolution) — against the live web standards and the actual implementation. Use when auditing or updating README/JSDoc in these packages, or when a doc claim (spec URL, ABNF, numeric count, algorithm description) is suspected stale. Trigger keywords: verify docs, doc audit, spec citation check, ABNF check, README accuracy, JSDoc accuracy.
    0
    installs
17. ▌
    Bench Triage · markuplint

    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 (steady state — the backlog is zero, so any entry is fresh intake), 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.
    0
    installs
18. ▌
    Markuplint Configure · markuplint

    Add, remove, or adjust Markuplint rules for specific files or elements. Analyzes violations, proposes scope-appropriate configuration changes, and confirms with the user.
    0
    installs
19. ▌
    Bench Maintain · markuplint

    Steady-state maintenance of the nu-validator coverage benchmark now that the nu-only backlog is zero: defend the invariants (nu-only = 0, orphan = 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, steady state bench.
    0
    installs
20. ▌
    List Rule Test · markuplint bundle

    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.
    0
    installs
21. ▌
    Product Manager · markuplint

    Analyze, review, and generate documentation for any repository from a Product Manager (PdM) perspective. Language- and framework-agnostic — works with any repository. Use this skill whenever you need to: understand repository structure, read and navigate code, analyze dependencies, generate or review READMEs and documentation, summarize the tech stack, evaluate architecture, assess operational impact of new features, or review PRs. Responds to requests like "what's going on in this repo?", "write a README", "review this change", "is this maintainable?", "what do you think of this PR?". If the task involves repository analysis, review, or documentation, use this skill without hesitation.
    0
    installs
22. ▌
    Bench Rule Enable · markuplint

    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.
    0
    installs
23. ▌
    Framework Parsers · markuplint

    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.
    0
    installs
24. ▌
    Bench Virtual Rule · markuplint

    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.
    0
    installs