diff --git a/doc/devel/coding_guide.rst b/doc/devel/coding_guide.rst
index ffac23812e95..7f96f845ba1b 100644
--- a/doc/devel/coding_guide.rst
+++ b/doc/devel/coding_guide.rst
@@ -1,5 +1,14 @@
 .. _pr-guidelines:
 
+.. raw:: html
+
+   <style>
+   .checklist { list-style: none; padding: 0; margin: 0; }
+   .checklist li { margin-left: 24px; padding-left: 23px;  margin-right: 6px; }
+   .checklist li:before { content: "\2610\2001"; margin-left: -24px; }
+   .checklist li p {display: inline; }
+   </style>
+
 ***********************
 Pull request guidelines
 ***********************
@@ -23,6 +32,8 @@ Summary for PR authors
 
 When making a PR, pay attention to:
 
+.. rst-class:: checklist
+
 * :ref:`Target the master branch <pr-branch-selection>`.
 * Adhere to the :ref:`coding_guidelines`.
 * Update the :ref:`documentation <pr-documentation>` if necessary.
@@ -53,6 +64,8 @@ Summary for PR reviewers
 
 Content topics:
 
+.. rst-class:: checklist
+
 * Is the feature / bugfix reasonable?
 * Does the PR conform with the :ref:`coding_guidelines`?
 * Is the :ref:`documentation <pr-documentation>` (docstrings, examples,
@@ -60,6 +73,8 @@ Content topics:
 
 Organizational topics:
 
+.. rst-class:: checklist
+
 * Make sure all :ref:`automated tests <pr-automated-tests>` pass.
 * The PR should :ref:`target the master branch <pr-branch-selection>`.
 * Tag with descriptive :ref:`labels <pr-labels>`.