Things Neo Can Do
Explore what makes Neo feel just like a real teammate
Documents
Code Review
Project Management
Attachments
Tickets
Code Repository
Comments
Pull Requests
- Reads system info on a bug
- Review PRs for typos
- Read steps to reproduce on a bug
- Comment on a ticket to confirm that it’s working on it
- Reply to comments with answers if they are questions
- Signal with reaction emoji (or text) that it is processing a PR comment
- Finds references to files from incomplete path names
- Understand long and complicated build error logs
- Run linters and prettifiers that fix code to correct its changes
- Look up tickets mentioned in a description
- Ask for help if a file or the codebase are extremely large
- Understand if a ticket comment is about project management or coding
- Ask for help if a PR is too large to review
- Learn branching policy, code style guidlines and code directory layout from configured context documents
- Automatically detect common linters and prettifiers
- Ignore binary files that it can’t edit or review
- Create PRs as drafts
- Understand PDF attachments
- Work with multiple repositories in one project
- Asks for help if it can’t find a specific file it thinks it needs
- Mark PRs as reviewed when it leaves no comments
- Delete files when editing code
- Detect CI build failures and send commits to fix them
- Follows links and reads attachments on PR comments
- Makes a PR with a new attempt when asked to retry a ticket
- Make new second attempt PR when reassigned a ticket, even if a PR already exists
- Remind you that you need to @ mention Neo if you try to talk to it on its own PR without the mention
- Adapt commit message format to team documentation
- Adjust rules for reviewing spelling in PRs to team documentation
- Say when a PR is too large to work directly on, and a new branch is needed
- Work with on-prem Jira Server as well as with Jira Cloud
- Work in parallel on bulk assigned tasks
- Follow links to files in a project code repository
- Fix build pipeline failures on any PR when asked to
- Follow links to files in a public or private repository
- Follows links to markdown resources in private repositories
- Contextualises static analysis tool findings to the code
- Runs security static analysis against code while reviewing
- Runs performance analysis against python code while reviewing
- Filters out false positives from static analysis tools
- Can use multiple private document managers
- Understand text file (.txt) attachments and links
- Review a PR when asked to in a comment
- Catches pitfalls reviewing code for common languages and frameworks
- Review Java code for common pitfalls
- Review Typescript code for common pitfalls
- Review CSS files for common pitfalls
- Review C# code for common pitfalls
- Review Python code for common pitfalls
- Revert commits by reference or description
- Cherry pick any commit
- Delete Git branches
- Rebase against another branch
- Create Git branches
- Read spreadsheet resources in CSV, XLS, XLSX and ODS files
- Create tickets with different types (bug, user story etc)
- Says when there are things it couldn’t do as part of a task, e.g. edit a binary file
- Edit very large files while coding
- Read Confluence short links of form /wiki/AAAAA
- Configure per-repository context documents
- Configure semantic linter rules per repository
- Refer to PRs as resources
- Configure not to approve PRs
- Review Kotlin code for common pitfalls, including Android-specific ones
- Use any custom field for repository selection
- Close/merge/approve PRs
- Modify custom fields in a work item
- Revert multiple commits on a PR
- Reads custom fields when assigned ADO work items
- Do one-off custom PR reviews based on rules in a comment
- Read context documents from .neo directory
- Reviewer proposes simple fixes
- Read build failures from TeamCity
- Call TeamCity self hosted when protected by Google IAP
- Review Swift code for common pitfalls
- Review PHP code for common pitfalls
- Review whether a pull request meets the specification in the ticket
- Find work item associated with PR when reviewing / coding on it
- Read build failures from Jenkins
- Use external CI (Jenkins, TeamCity) via Bitbucket and GitLab
- Confirm what has been checked when doing one-off custom reviews
- Learn rules on what build failures to fix from team documentation
- Configure not to fix build failures
- Learn how to plan its coding, such as writing tests, from team docs
- Reference default branch name when choosing branch names
- Suggest single line changes with simple interface to accept in all code repository tools
- Reads any image format - e.g. gif, tiff, bmp
- Reads documents from ADO wiki
- Can squash all commits from one PR into one
- Remove labels from tickets
- Use architecture diagrams provided as part of the specification
- Create new files when generating code
- Review PRs for whether they meet a ticket’s specification
- Learn branch naming conventions from team documentation
- Comment on a PR to say it has started / finished a review
- Modify files when editing code
- Infer branch naming conventions from recent branches and PRs
- Follow workflow allowed ticket transitions only
- Detect if there’s already a branch to use for a PR
- Use build log failures to try to fix them