When you job hop a lot, you become very adaptable. I can start contributing high quality code after the first week. I can internalise the coding conventions and all the nuances of the code base straight away because I've seen it all and I understand the different team mindsets and dynamics really well.
Being adaptable and delivering a few one off features is junior engineering which senior engineers can coach through. Coding conventions differ from team to team, package to package adapting to these also doesn't mean you are a robust engineer. It means you are competent. Solid engineer are expected to adapt. All big software projects that stand the test of time have nuances and even possibly anti-patterns because the initial design missed something.
I'm not sure what you mean by "saw the kinds of companies I worked for" but if you worked at Google for 6 months, Facebook for 6 months and Amazon for 6 months it still wouldn't mean much to me. All it means is you are smart enough to get your foot in the door but not successful enough to succeed.
99.9% of the time, the single-company mindset that you're suggesting just gets people stuck in a rut (I've seen it). If you've had a different experience then you're one of the lucky ones.
Job Hopping every six months translates to 'cant be trusted with any serious work'.
In India its more or less a given, that your resume won't even make it past the screening stage.