Robot Command Language (RCL) for ChatGPT + GitHub Reviews
March 18th, 2026 2:18 PM Mr. Q Categories: Programming
Use this when you want your repo reviews to behave like a structured robot system instead of loose prompts.
What RCL Does
RCL turns your review workflow into a small command language with:
- a clear command name
- a target repo
- an optional scope
- an action
- an output format
This makes your prompts shorter, cleaner, and easier to reuse.
RCL Structure
Use the GitHub connector on the target repository.
COMMAND: <command_name>
REPO: <owner/repo>
SCOPE: <file | folder | system | latest | commits | full>
FOCUS: <physics | collision | lifecycle | performance | architecture | bugs | general>
OUTPUT: <review | plan | tasks | summary | rewrite>
Then:
- perform the requested review
- return the result in the requested format
Start Session Command
Use the GitHub connector on the target repository.
COMMAND: START_SESSION
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: full
FOCUS: general
OUTPUT: review_state
Then:
- map the repo
- identify major systems
- review recent commits
- create and maintain:
- Repo Map
- Current Priorities
- Open Issues
- Suggested Refactors
- Performance Risks
- Next Best Actions
Continue Session Command
Use the GitHub connector on the target repository.
COMMAND: CONTINUE_SESSION
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: latest
FOCUS: general
OUTPUT: review_state
Then:
- update the current review state
- tell me the single best thing to work on next
Repo Map Command
Use the GitHub connector on the target repository.
COMMAND: MAP_REPO
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: full
FOCUS: architecture
OUTPUT: summary
Then:
- show high-level structure
- identify entry points
- identify key engine files
- suggest review order
Latest Commits Command
Use the GitHub connector on the target repository.
COMMAND: REVIEW_COMMITS
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: last_5
FOCUS: general
OUTPUT: review
Then:
- summarize each commit
- identify bugs, risks, and regressions
- highlight the most important changes
Deep Physics Command
Use the GitHub connector on the target repository.
COMMAND: REVIEW_SYSTEM
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: physics
FOCUS: physics
OUTPUT: review
Then:
- analyze correctness
- identify weak spots
- suggest fixes
- prioritize the most critical issues
Collision Command
Use the GitHub connector on the target repository.
COMMAND: REVIEW_SYSTEM
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: collision
FOCUS: collision
OUTPUT: review
Then:
- identify edge cases
- call out bad assumptions
- recommend exact fixes
Object Lifecycle Command
Use the GitHub connector on the target repository.
COMMAND: REVIEW_SYSTEM
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: object_lifecycle
FOCUS: lifecycle
OUTPUT: review
Then:
- analyze
ObjectDynamic,ObjectKillable, and related classes - identify design weaknesses
- recommend fix vs refactor vs rewrite
File Review Command
Use the GitHub connector on the target repository.
COMMAND: REVIEW_FILE
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: <path/to/file>
FOCUS: general
OUTPUT: review
Then:
- explain purpose
- identify bugs
- identify performance issues
- recommend improvements
Example:
Use the GitHub connector on the target repository.
COMMAND: REVIEW_FILE
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: src/physics.js
FOCUS: physics
OUTPUT: review
Then:
- recommend specific improvements
Folder Review Command
Use the GitHub connector on the target repository.
COMMAND: REVIEW_FOLDER
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: <folder>
FOCUS: general
OUTPUT: review
Then:
- explain architecture
- identify responsibilities
- identify weakest area
Bug Hunt Command
Use the GitHub connector on the target repository.
COMMAND: SCAN_BUGS
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: full
FOCUS: bugs
OUTPUT: tasks
Then:
- list likely bugs
- rank them by severity
- suggest where to inspect first
Performance Command
Use the GitHub connector on the target repository.
COMMAND: SCAN_PERFORMANCE
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: full
FOCUS: performance
OUTPUT: review
Then:
- identify bottlenecks
- rank the biggest performance risks
- suggest optimizations
Fix Plan Command
Use the GitHub connector on the target repository.
COMMAND: PLAN_FIXES
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: current_state
FOCUS: general
OUTPUT: tasks
Then:
- convert issues into an ordered fix plan
- include files involved, risk, and priority
Rewrite Plan Command
Use the GitHub connector on the target repository.
COMMAND: PLAN_REWRITE
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: weakest_subsystem
FOCUS: architecture
OUTPUT: rewrite
Then:
- identify the weakest subsystem
- propose a better design
- include migration steps
- say whether to do it now or later
Save Planning Commands
Save Current State
Use the GitHub connector on the target repository.
COMMAND: SAVE_STATE
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: current_state
FOCUS: general
OUTPUT: saved_state
Then:
- treat the current review state as the source of truth for this chat
Export Markdown
Use the GitHub connector on the target repository.
COMMAND: EXPORT_STATE
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: current_state
FOCUS: general
OUTPUT: markdown
Then:
- convert the current review state into clean markdown
Export Task List
Use the GitHub connector on the target repository.
COMMAND: EXPORT_TASKS
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: current_state
FOCUS: general
OUTPUT: tasks
Then:
- convert the current review state into a prioritized checkbox list
Export WordPress Version
Use the GitHub connector on the target repository.
COMMAND: EXPORT_WORDPRESS
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: current_state
FOCUS: general
OUTPUT: wordpress
Then:
- convert the current review state into a WordPress Classic Editor post
Daily RCL Command
Use the GitHub connector on the target repository.
COMMAND: DAILY_REVIEW
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: latest
FOCUS: physics, collision, lifecycle, performance
OUTPUT: review_state
Then:
- update the review state
- tell me what to fix next
Best Practical Workflow
New chat
Run START_SESSION
During normal work
Run DAILY_REVIEW
When debugging
Run SCAN_BUGS or REVIEW_SYSTEM
When planning work
Run PLAN_FIXES
When redesigning
Run PLAN_REWRITE
When you want to keep the results
Run SAVE_STATE or one of the export commands
Ultra-Compact Version
Use the GitHub connector on the target repository.
COMMAND: START_SESSION
REPO: ToolboxAid/HTML-JavaScript-Gaming
SCOPE: full
FOCUS: physics, collision, lifecycle, performance, architecture
OUTPUT: review_state
Then:
- keep the session active
- tell me what to fix first
Naming Rules for Any Repo
Replace only this line:
REPO: ToolboxAid/HTML-JavaScript-Gaming
Examples:
REPO: myname/project-alpha
REPO: ToolboxAid/some-other-repo
REPO: org/repo-name
Why RCL Is Better
- more structured than normal prompts
- easier to reuse across repos
- fits your robot-system mindset
- easier to save, extend, and standardize
If you want, I’ll turn this into your final WordPress-ready Classic Editor HTML version with your preferred formatting style.