The '(Code Review)' link should be rendered with the extra links + It should be 'Code review' instead of 'Code Review'

It makes sense but it's just lower priority at the moment. If anyone wants to provide a patch then that might get it in faster.

I'm happy to, but provide a patch if you want to see it happen sooner.

Adding a link can not be accomplished without a core patch or a patch to your site's administrative theme. As discussed in #913712: Improve modules page table poor layout., while enabling more links, it would make sense to stack the links, as this patch to core does.

The attached patch for this module, along with the core patch above, would make this happen. Unless and until core was patched, you could copy the patched core theme function, theme_system_modules_fieldset(), to your administrative theme. It would look like:

function mytheme_system_modules_fieldset($variables) {
  $form = $variables['form'];

  // Individual table headers.
  $rows = array();
  // Iterate through all the modules, which are
  // children of this fieldset.
  foreach (element_children($form) as $key) {
    // Stick it into $module for easier accessing.
    $module = $form[$key];
    $row = array();
    unset($module['enable']['#title']);
    $row[] = array('class' => array('checkbox'), 'data' => drupal_render($module['enable']));
    $label = '<label';
    if (isset($module['enable']['#id'])) {
      $label .= ' for="' . $module['enable']['#id'] . '"';
    }
    $row[] = $label . '><strong>' . drupal_render($module['name']) . '</strong></label>';
    $row[] = drupal_render($module['version']);
    // Add the description, along with any modules it requires.
    $description = drupal_render($module['description']);
    if ($module['#requires']) {
      $description .= '<div class="admin-requirements">' . t('Requires: !module-list', array('!module-list' => implode(', ', $module['#requires']))) . '</div>';
    }
    if ($module['#required_by']) {
      $description .= '<div class="admin-requirements">' . t('Required by: !module-list', array('!module-list' => implode(', ', $module['#required_by']))) . '</div>';
    }
    $row[] = array('data' => $description, 'class' => array('description'));
    // Display operation links (such as help or permissions) in one column.
    $row[] = array('data' => drupal_render($module['links']), 'class' => array('operations'));
    $rows[] = $row;
  }

  return theme('table', array('header' => $form['#header'], 'rows' => $rows));
}

I spent an hour on this, and agree it's difficult to do now. The only way I could get the link in the right column is if we change the #theme from system_modules_fieldset to something like coder_modules_fieldset, and then completely re-implement the theme function in coder. This seems too hacky for me, so leaving it as-is until core solves the problem.

I did change references to "Code Review" to "Code review".

Done in 7.x-2.x but apparently at least one person doesn't like it, see #1775954: "Code Review" operations on the module administration page

The problem with the Operations table is that it doesn't scale. Every additional column requires a fixed large amount of horizontal space (English is typically quite short, other languages are considerably longer!) and we end up with a large fixed matrix like the Permissions page. The only way to deal with that pattern is to buy a larger monitor, which is not a good solution.

Operations is actually worse than Permissions, because Permissions at least uses every cell, while operations require space even when most cells in the column are empty. And the Modules page first squishes the Descriptions column so that the rows become unbearably high before a scrollbar appears.

Thank you for the extensive explanation, klonos!

These are nice UI features and yes, I'll be happy with them. If Coder were a production module, I'd say it ought to wait until these features are available (Don't buy that Hummer before widening your driveway! :)), but it's a development tool and it doesn't need to be enabled unless you're actually using it.

It still is a pain for developers who are confined to a less than huge screen for whatever reasons, but progress wins over considerateness, I guess.