I suggest simplifying the code as much as possible, so that it is easier to understand. Exactly what that means will depend on the content of your clauses.
For example, it might be clearest to pull out code as you suggest, although having a combination of continue
vs. not-continue
clauses has the potential to confuse readers of the code. Another alternative might be to extract the repeated code into a separate method and call it where necessary, which has the advantage that you can give it a meaningful name.
However, you've described this code as a long if
... else if
chain with long clauses. This is a code smell and suggests that deeper refactoring might be necessary for it to be maintainable. For example, consider using the strategy pattern.