diff --git a/docs/retriggering.md b/docs/retriggering.md
index 0b6d9962a..1fe045739 100644
--- a/docs/retriggering.md
+++ b/docs/retriggering.md
@@ -9,6 +9,11 @@ to trigger the Packit job manually.
 
 ![Re-run GitHub check](img/retriggering/comment.png)
 
+### help
+Packit is able to provide a help message summarizing all available commands and options:
+
+    /packit help
+
 ### copr_build
 For retriggering the [`copr_build`](/docs/configuration/upstream/copr_build) jobs, Packit is able to trigger new builds based on a pull request comment:
 
diff --git a/fedora-ci/retriggering.md b/fedora-ci/retriggering.md
index 1624cd1e7..8cfe14c22 100644
--- a/fedora-ci/retriggering.md
+++ b/fedora-ci/retriggering.md
@@ -5,6 +5,12 @@ sidebar_position: 2
 
 You can retrigger CI jobs in dist-git pull requests by posting comments that include the appropriate `/packit-ci` commands, as outlined below.
 
+## Help
+
+Packit is able to provide a help message summarizing all available commands and options:
+
+    /packit-ci help
+
 ## Scratch builds
 
 To retrigger a scratch build, add the following comment to the pull request: