Things Neo Can Do
Explore what makes Neo feel just like a real teammate
Code Review
Comments
Code Repository
Pull Requests
Tickets
Documents
Attachments
Project Management
- Pitfalls reviewing for PHP
- Pitfalls reviewing for Swift
- Read build failures from TeamCity
- Ephemeral Review Guidelines
- Refer to PRs as resources
- Per-repository context documents
- Can reference public resources for onboarding documents
- Read spreadsheet resources in CSV, XLS, XLSX and ODS files
- Delete Git branches
- Create Git branches
- Rebase against another branch
- Cherry pick any commit
- Revert commits by reference
- Pitfalls reviewing for CSS
- Pitfalls reviewing for C#
- Pitfalls reviewing for Typescript
- Pitfalls reviewing for Python
- Pitfalls reviewing for Java
- Find markdown resources on private repos
- Find code resource references on public repos
- Find code resource references on a private repo
- Can be explicitly asked to fix build failures
- Can use a code repository as a document manager
- Works in parallel on bulk assigned tasks
- Say when a PR is too large and so it can’t work on it, instead make a new branch against it
- Works with on-prem version of Jira as well as cloud
- Tell you when someone else has taken over its PR by committing to it, and you ask it to do something
- Make new second attempt branch even if a branch already exists when assigned work item
- Learn spelling rules from context documents for reviews
- Learn commit message format from context documents
- Understands ticket comments to retry
- Follows resources on PR comments
- Mark PRs are reviewed when it leaves no comments
- Stops auto replying to comments on PRs where the last comment is not authored by Neo
- AskForHelp if it can’t find a specific file it thinks it needs
- Can work with multiple repositories
- Creates PRs as Draft
- Understands PDF files attached to tickets
- Automatically detect common linters and prettifiers
- Learn branching policy, code style guidlines and code directory layout from configured context documents
- Understand if a ticket comment is about project management or coding
- Ask for help if a file or the codebase are too large
- Understands tickets mentioned in a description
- Find 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
- Signals with icons (or text) that it is processing a PR comment
- Replies to comments with code or answers if they are questions
- Concurrently handle tasks and comments on the same ticket or PR
- Respond to @ mention on someone else’s PR
- Respond to @ mention on a ticket it isn’t assigned to
- Reviews using semantic linter rules
- Can be assigned as reviewer to a PR
- Adds links in comments of tickets and PRs to refer to each other
- Gets context from any parent issue recursively
- Use architecture diagrams provided as part of the specification
- Uses templates to generate PR summaries
- It can send code to any PR if @mentioned from a comment
- Uses the build log failures to try to fix them
- Copes with many build failures at once
- Detects CI build failures and sends commits to fix them
- Understand Figma files
- Support of all common software team tools
- Comments on the PR when done with the code review
- Comments on the PR when reviewing code
- Marks a PR as reviewed when it finishes reviewing it
- Detects if there’s already a branch to use for a PR
- Learns branch naming conventions from history
- Learns branch naming conventions from docs
- Can create PRs where base and head branches can be new or existing
- Learns workflows from documentations
- Follows workflow allowed transitions
- Updates the status of tickets it’s working on (TODO→DOING→DONE)
- Can break down a User Story in sub-tasks
- Can remove labels to tickets
- Can create branches
- Can add labels to tickets
- Searches repositories to efficiently find what files to work on
- Can create and edit arbitrarily large files
- Can delete files
- Can modify files when editing code
- Can create new files when generating code
- Handles arbitrarily large codebases
- Smartly navigates codebases for code selection
- Finds relevant files to work on from a codebase regardless of the size
- Can assign a ticket to itself
- Tells the user when something prevents it from completing the work
- Comments to a ticket to confirm that it’s working on it
- Links tickets in any system with PRs in any system
- Write PR summaries summarising the changes
- Write commit messages summarising the changes
- Sends code addressing comments on PRs it opened
- Reads branching policies from documents
- Reads context docs with instructions
- Link to a markdown file in a docs repo
- Can assign a ticket to another team member
- Understands docx attachments
- Understand image attachments
- Reads system info on a bug
- Read steps to reproduce on a bug