Recommend buildifier instead of skylint as the official linter
PiperOrigin-RevId: 251832142
diff --git a/site/docs/skylark/bzl-style.md b/site/docs/skylark/bzl-style.md
index e6f4839..61e729a 100644
--- a/site/docs/skylark/bzl-style.md
+++ b/site/docs/skylark/bzl-style.md
@@ -38,7 +38,8 @@
## General advice
-* Use [skylint](skylint.md).
+* Use [Buildifier](https://github.com/bazelbuild/buildtools/tree/master/buildifier#linter)
+ as a formatter and linter.
* Follow [testing guidelines](testing.md).
## Style
diff --git a/site/docs/skylark/faq.md b/site/docs/skylark/faq.md
index 59cdbbf..d90bc95 100644
--- a/site/docs/skylark/faq.md
+++ b/site/docs/skylark/faq.md
@@ -77,8 +77,8 @@
For rules and rule attributes, you can pass a docstring literal (possibly
triple-quoted) to the `doc` parameter of `rule` or `attr.*()`. For helper
functions and macros, use a triple-quoted docstring literal following the format
-given [here](skylint.md#docstrings). Rule implementation functions generally do
-not need their own docstring.
+given [here](https://github.com/bazelbuild/buildtools/blob/master/WARNINGS.md#function-docstring).
+Rule implementation functions generally do not need their own docstring.
Using string literals in the expected places makes it easier for automated
tooling to extract documentation. Feel free to use standard non-string comments
diff --git a/site/docs/skylark/skylint.md b/site/docs/skylark/skylint.md
index 078a372..0cc3cee 100644
--- a/site/docs/skylark/skylint.md
+++ b/site/docs/skylark/skylint.md
@@ -5,10 +5,11 @@
# Skylint
-This document explains how to use Skylint, a Starlark linter.
+ -->
-Skylint is no longer maintained. It will be replaced soon with [Buildifier](
-https://github.com/bazelbuild/buildtools/tree/master/buildifier#linter).
+Skylint is deprecated in favor of [Buildifier](https://github.com/bazelbuild/buildtools/tree/master/buildifier#linter)
+
+This document explains how to use Skylint, a Starlark linter.
<!-- [TOC] -->
