@robot-inventor/agent-skills 0.8.0 → 0.9.0

package/hooks/hooks.json

@@ -2,7 +2,19 @@
     "hooks": {
         "SessionStart": [
             {
-                "matcher": "startup|resume|clear|compact",
+                "matcher": "compact",
+                "hooks": [
+                    {
+                        "type": "command",
+                        "command": "bun \"${PLUGIN_ROOT}/scripts/codex.ts\"",
+                        "commandWindows": "powershell -NoProfile -NonInteractive -Command \"& bun (Join-Path $env:PLUGIN_ROOT 'scripts/codex.ts')\"",
+                        "additionalContextLimit": 0
+                    }
+                ]
+            }
+        ],
+        "UserPromptSubmit": [
+            {
                 "hooks": [
                     {
                         "type": "command",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@robot-inventor/agent-skills",
-  "version": "0.8.0",
+  "version": "0.9.0",
   "description": "Roboin's personal collection of Agent Skills.",
   "homepage": "https://github.com/Robot-Inventor/agent-skills#readme",
   "bugs": {

package/skills/review-loop/SKILL.md

@@ -26,9 +26,9 @@ The following is the core of this skill; please follow the specified steps.
 
 Request a code review from the subagent.
 
-If you have the option to choose whether to fork the context or launch the subagent in an isolated context when starting it, **always** launch it in an isolated context. Forking the context would be equivalent to a self-review, so you need to launch a subagent in an isolated context to review it from a different perspective.
+If you have the option to choose whether to fork the context or launch the subagent in an isolated context when starting it, **always** launch it in an isolated context. When requesting a review from a sub-agent, be sure to provide them with an overview of the task requested by the user, and instruct them to thoroughly review the changes made to the current workspace.
 
-When requesting a review from a sub-agent, be sure to provide them with an overview of the task requested by the user, and instruct them to thoroughly review the changes made to the current workspace.
+Code reviews by sub-agents can take time. Please note that if you re-spawn a sub-agent currently undergoing a review simply because it has not yet responded, the review process will start over from scratch, resulting in even longer wait times. If the workspace contains a mix of changes made by you and by the user, please specify the files to be reviewed when submitting your review request.
 
 ### 2. Receive reviews and improve your code
 

package/skills/simple-engineering/SKILL.md

@@ -25,3 +25,7 @@ Reinventing the wheel should be avoided. Before adding code, check whether exist
 Keep the YAGNI (You aren't gonna need it) principle in mind. You should not introduce complexity just because you might need it in the future. Also, there is no need to maintain backward compatibility for unreleased features.
 
 The code ultimately delivered to the user should be such that every line of change is necessary and no unnecessary code remains. Carefully review the diff line by line, rather than file by file, to ensure that all changes are truly necessary.
+
+## Establish a shared understanding
+
+If `request_user_input` tool is available, actively use it when asking the user questions, especially while running the grilling session. Do not use it for a single yes/no question; instead, use it when asking multiple questions at once or when presenting multiple options.