Clear Tickets, Turned Into Tested PRs
Assign a well-described bug or small feature, and get back a pull request with the implementation and tests.
Small Tickets Wait Behind Big Ones
Well-described bugs and small features can wait behind larger projects. The ticket may already explain the change and its acceptance criteria, but someone still has to implement and test it.
Assign It, Review the PR
Start an agent from a Linear or Jira issue event, or a manual request. Give it the ticket and ask it to follow the repository's conventions, implement the change, run targeted tests, and prepare a pull request for review.
Show last login date on the profile page
3 tests added, checks passed
Common Questions
Which tickets work best?
Well-described bugs and small features with clear acceptance criteria. The clearer the ticket, the better the result.
Which issue trackers are supported?
Linear, Jira Cloud, and Jira Server issue events can start an automation. Jira Cloud webhook setup requires Felan support; Jira Server requires manual setup. Integrations also include Asana tasks and events, Azure DevOps Boards, and ClickUp tasks. Include clear requirements and acceptance criteria.
Does it follow our conventions?
Felan discovers the repository's structure, package manager, conventions, and project instructions before changing files. Include your project instructions and review the result against them.
Which models can it use?
Any major provider, plus local and private models. Bring your own keys or subscription, and there's no markup on tokens.
Related: Software engineering docs, First-pass code review.
Keep Your Attention for the Hard Problems
Start with one repo and one recurring task.