There is a configuration option for disabling that feature. Just set "jsdocs_extend_double_slash": false in your Base File.sublime-settings (or Preferences.sublime-settings if you're on the dev branch). The other option is to press Shift+Enter and it won't extend the comment.

The deep alignment is pretty close, but there's a few differences from what my company's code-sniffing will accept, namely that we don't align the first column with other tags. So, when there's @param and @return, this plugin's deep alignment puts two spaces after the @param, but the code sniffer wants just one.

Also, we do a newline after the descriptions, but no newline before the @return tag.

Really, this is awesome, though - not a big deal to fix those myself, and much better than typing out the whole thing!

I believe that at least some of your requests are already implemented -- you just need to set a config variable. The docs are in the readme and all the options are documented at the bottom of that page.

jsdocs_align_tags (String) Whether the words following the tags should align. Possible values are 'no', 'shallow' and 'deep'

For backwards compatibility, false is equivalent to 'no', true is equivalent to 'shallow''shallow' will align only the first words after the tag. eg:

Unfortunately, all three settings aren't quite what we need - which may indicate we should change the code-sniffing standard! Deep alignment is closest - we do align columns, but only within the same tag, not across all tags like deep does. Actually, shallow aligns the first column across all tags, too. "No" means I have to manually align all the columns, which really isn't the end of the world.