Commit
A message grounded in the diff.
/commit reads staged changes and generates a message. Review, edit or decline it before committing – the explanation should match the change.
Git & GitHub
Keep the context. From issue to pull request.
An issue, a branch diff, a commit message and review comments should not be four disconnected tasks. Bring them into the project workflow – and keep the decisions visible.
GitHub workflows require GitHub CLI (gh), authentication and the appropriate repository permissions. Run slash commands inside Lurus Code chat.
The path of a change
- Understand the issue
- Make the change
- Prepare the commit
- Open a draft PR
From project context to a handoff
Create commit messages and pull requests from your changes.
Pull request
Give reviewers a starting point.
/create-pr uses your branch commits and diff to prepare a title and description. Use --draft when the change needs another look before review.
The work continues after the first diff
Automate bug fixing – from understanding the issue to the fix.
Understand an issue first.
/analyze-issue 42 /analyze-issue reads an issue and asks for an analysis of the cause, affected code and a possible approach, without requesting source edits.
Work on the fix.
/fix-issue 42 /fix-issue loads the issue, prepares a fix branch and hands the implementation task to the agent. Inspect and test the result.
Address review comments.
/fix-pr /fix-pr brings open comments on the current PR into the agent workflow. Check that the resulting changes address the intended feedback.
Start locally. Publish deliberately.
Start with a real issue or a small staged change.
For Pro, Pro+ and Ultra. Paid subscription after the trial unless you cancel beforehand. Usage and features depend on your plan and credit.
AI-generated fixes and descriptions need review. GitHub commands can create branches and publish pull requests; use them intentionally.
- Understand an issue first.
/analyze-issue 42 - Generate a message for staged changes
/commit - Create a draft pull request
/create-pr --draft
Your code stays yours.
Source code and request context are processed with Zero Data Retention. No use for model training. Providers and processing regions are disclosed transparently.
See privacy and processing detailsA few things to know before you start.
What do the GitHub workflows need?
Install GitHub CLI (gh), authenticate it and use an account with the appropriate repository permissions. Plain Git commits require a local Git repository.
Can I analyse an issue before changing code?
Yes. /analyze-issue requests read-only analysis. /fix-issue starts a fix workflow and can create a branch and source changes.
Does the AI decide what gets merged?
No. Review the diff and generated descriptions, run your checks and keep your repository approval rules. A draft PR is not an approved merge.
Git & GitHub
Move a real change forward. With its context.
Try the workflow in your repository. Begin with issue analysis or a small diff before handing over a larger change.
For Pro, Pro+ and Ultra. Paid subscription after the trial unless you cancel beforehand. Usage and features depend on your plan and credit.
Want to start with your team? Talk to us.