Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

lint

Étoiles21

Forks44

Mis à jour28 avril 2026 à 11:50

Auto-fix all formatting issues in the docs-builder repo — runs dotnet format for C# and npm fmt:write for TypeScript/JS. Use when the user asks to fix formatting, lint the code, or when a pre-commit hook fails due to formatting.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

elastic

elastic/docs-builder

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	lint
description	Auto-fix all formatting issues in the docs-builder repo — runs dotnet format for C# and npm fmt:write for TypeScript/JS. Use when the user asks to fix formatting, lint the code, or when a pre-commit hook fails due to formatting.

Lint Skill

Fixes all formatting issues across C# and TypeScript in the docs-builder repo.

Steps

1. Fix C# formatting

dotnet format

This applies the project's editorconfig and code style rules to all C# files.

2. Fix TypeScript/JS formatting

cd src/Elastic.Documentation.Site && npm run fmt:write

This runs Prettier on all frontend source files.

3. Report results

After both commands complete:

If files were changed: list which files were reformatted
If nothing changed: confirm "No formatting issues found"

Notes

This skill fixes files in place but does not commit
Run this before /commit if you see formatting errors in build output or pre-commit hook failures
Formatting rules are enforced by Husky.Net pre-commit hooks (prettier + eslint for TS, dotnet-lint on pre-push for C#)
dotnet format is also available as ./build.sh lint for the full lint pipeline

Plus depuis ce dépôt

même dépôt

commit

elastic/docs-builder

Stage relevant files and create a well-formed git commit for the docs-builder repo. Use this when the user asks to commit changes, save work, or create a commit.

2026-04-2821

elastic/docs-builder

Create a GitHub pull request for the current branch with a focused why/what body and exactly one release-drafter label. Use when the user asks to open a PR, create a pull request, or ship a branch.

2026-04-2821

style-review

elastic/docs-builder

Review changed or staged C# code against the docs-builder coding standards and flag violations. Use when the user asks to review code style, check for standards violations, or audit a diff before committing.

2026-04-2821

test

elastic/docs-builder

Run the relevant tests for what changed — detects whether to run C# unit tests, specific test projects, integration tests, or JS/TS tests based on changed files. Use when the user asks to run tests, verify changes, or check if something is broken.

2026-04-2821

mcp-search

elastic/docs-builder

Search, analyze, and author Elastic documentation using the remote MCP server. Use this when the user asks about Elastic product documentation, features, or APIs; wants to find, read, or verify existing docs pages; is writing or editing documentation; mentions cross-links between repos; asks about documentation structure, coherence, or consistency; wants to generate templates following Elastic content type guidelines; or references elastic.co/docs URLs or Elastic product names.

2026-02-1921

name	lint
description	Auto-fix all formatting issues in the docs-builder repo — runs dotnet format for C# and npm fmt:write for TypeScript/JS. Use when the user asks to fix formatting, lint the code, or when a pre-commit hook fails due to formatting.

Lint Skill

Fixes all formatting issues across C# and TypeScript in the docs-builder repo.

Steps

1. Fix C# formatting

dotnet format

This applies the project's editorconfig and code style rules to all C# files.

2. Fix TypeScript/JS formatting

cd src/Elastic.Documentation.Site && npm run fmt:write

This runs Prettier on all frontend source files.

3. Report results

After both commands complete:

If files were changed: list which files were reformatted
If nothing changed: confirm "No formatting issues found"

Notes

This skill fixes files in place but does not commit
Run this before /commit if you see formatting errors in build output or pre-commit hook failures
Formatting rules are enforced by Husky.Net pre-commit hooks (prettier + eslint for TS, dotnet-lint on pre-push for C#)
dotnet format is also available as ./build.sh lint for the full lint pipeline