You mean below at L104?  

It's pretty much the same effect as the ```action_variable``` case, but parses the controller name from ```second_arg``` instead of using @current_controller.  

It works in testing on routes like:
```ruby
match '/test/:action', controller: 'test'
```
where I get a result like:
```
+------------+----------------+----------------+------------------------------------------------------------------------------->>
| Confidence | Controller     | Warning Type   | Message                                                                       >>
+------------+----------------+----------------+------------------------------------------------------------------------------->>
| Medium     | TestController | Default Routes | Any public method in TestController can be used as an action for matched reque>>
+------------+----------------+----------------+------------------------------------------------------------------------------->>
```

line 100 takes care of true defaults like:
```ruby
match '/:controller/:action'
```
which yields:
```
+------------+-------+--------+----------------+------------------------------------------------------------------------------->>
| Confidence | Class | Method | Warning Type   | Message                                                                       >>
+------------+-------+--------+----------------+------------------------------------------------------------------------------->>
| High       |       |        | Default Routes | All public methods in controllers are available as actions in routes.rb near l>>
+------------+-------+--------+----------------+------------------------------------------------------------------------------->>
```

If there's a case that's broken, I'm not seeing it.  We have to return ```exp``` in the default case, so the line number can be parsed later.  ```action_variable``` will only trigger the controller action case, not the true default case.