[skip ci] "Get checks status" command

.cursor/commands/create-pr.md

@@ -4,6 +4,9 @@
 Create a well-structured pull request with proper description, labels, and reviewers.
 
 ## Steps
+
+_Note_ in the command output, format all URLs as clickable Markdown links: `[Link Text](URL)`
+
 1. **Check that the pull request is not already open in the remote repository**
    - If it is opened, write only PR summary (see step 3) and skip all other steps
 

.cursor/commands/deploy-demo.md

@@ -5,6 +5,8 @@ Create Github deployment for current branch using `.github/workflows/deploy-revi
 
 ## Steps
 
+_Note_ in the command output, format all URLs as clickable Markdown links: `[Link Text](URL)`
+
 1. **Ensure all changes are pushed to remote**
 
 2. **Check if there is a running deployment workflow for current branch**

.cursor/commands/get-checks-status.md

@@ -0,0 +1,17 @@
+# Get Checks Status
+
+## Overview
+Fetch the status of the "Checks" workflow run (workflow file `.github/workflows/checks.yml`) for __current branch__.
+
+## Steps
+
+_Note_ in the command output, format all URLs as clickable Markdown links: `[Link Text](URL)`
+1. **Fetch the status of the most recent workflow run**
+    - Use the GitHub API to get the workflow status for the *current branch*.
+    - If the workflow is pending, subscribe to its completion.
+    - If the workflow has failed, retrieve the list of all failed jobs and steps.
+    - If the workflow was never run for the current branch, report that and skip other steps.
+
+2. **Report the status with a system notification**
+   - Upon workflow completion, notify with the final status (success or failure).
+   - In case of failure, notify about the error along with the list of failed jobs and steps.