I have Master and Develop branch, developers are commit their code on Develop branch at the time of release some commits which is in develop branch not going for release so i have skip that commits while creating release branch or merging on master branch which is a best approach to handle this case.
It seems the command you're looking for is git cherry-pick.
From git-cherry-pick(1):
Given one or more existing commits, apply the change each one introduces, recording a new commit for each. This requires your working tree to be clean (no modifications from the HEAD commit).
You checkout the target HEAD, keeping your WD clean, and run git cherry-pick <commit> <commit> ... and Git will do the rest. In case of a conflict, just solve it as usual.