Lingxi's Engineer Bot
Created by Lingxi Li
Coordinate cloud coding agents and track pull requests through to human review.
Our developer take
Supervising multiple coding tasks
A useful candidate when you can specify work clearly but lose time checking multiple agents and PRs. Start with a single issue and define what counts as ready for review, including passing checks and evidence that the change works.
A practical first workflow
How to use Lingxi's Engineer Bot
Take one well-defined issue from assignment to a review-ready PR.
An AI IDE List walkthrough based on the linked template. These are suggested tasks and review criteria, not results from a hands-on test.
First, add this Bot
Open the official Lingxi's Engineer Bot template, choose Import Bot, and finish adding it in the Grok Bot app. Open its conversation, then follow the workflow below. If you have not set up the app, follow our installation and connection guide.
What to prepare
- Repository URL, framework, and repository-host authentication.
- One issue with acceptance criteria and the commands used by CI.
- Your cloud-agent setup; a Notion board is optional.
Complete repository onboarding
Share the repository and stack, complete authentication, and explain which cloud agents are available. State whether you want the optional Notion board.
Define ready for review
Choose one issue and specify the required behavior, tests, and proof. For a UI change, request screenshots of the affected state.
Delegate and inspect progress
Ask the Bot to coordinate the issue and link the agent task or PR. Review blockers and requested decisions before adding parallel work.
Check the handoff and watcher
Inspect the diff and CI evidence. Confirm the 30-minute PR watcher created during onboarding; merging remains your decision.
First-run example
Replace every [BRACKETED_VALUE] with your details, attach the required files, then send this in the Bot's conversation.
Coordinate [ISSUE_URL] in [REPO_URL], using [FRAMEWORK]. Acceptance criteria: [EXPECTED_BEHAVIOR]. Required checks: [TEST_AND_BUILD_COMMANDS]. Available cloud agent: [AGENT_SETUP]. I do not need a Notion board for this task. Start with a plan and identify missing access. Then coordinate one implementation and return the PR link, check results, and proof for each acceptance criterion. Report any unverified criterion explicitly. Leave the merge to me and confirm how the PR watcher is configured.
What you should get
Use this checklist to review the first result and request anything missing.
- One issue linked to an implementation task and PR.
- Acceptance criteria paired with test results or other review evidence.
- An explicit ready-for-review or blocked status and watcher configuration.
For the next run
Add another issue once the first handoff meets your review criteria. Reuse that definition of ready across tasks.
If the first run gets stuck
If a watcher is missing, finish repository authentication and ask about onboarding. The public template does not ship with a preinstalled watcher.
What the template includes
Official sourceSummarized from the public listing. The labels below describe capabilities; exact installed skill and connector names are not always published.
Integrations & inputs
- GitHub / repository host
- Cloud agents
- Notion (optional)
Skills & playbooks
Task coordination · PR readiness checks
Routines
A 30-minute PR watcher is created during onboarding after repository authentication; it is not preinstalled.
What to consider
The template leaves merging to the human. Agree on review criteria before delegating several tasks at once.