I depends on what you are trying to accomplish.
I you want to create an abstraction layer between Entity Framework and your business logic, then yes, it's a good idea. But then you have to do a complete abstraction meaning that your repository classes can not expose IQueryable<T>
.
If you don't create a complete abstraction, then I do not see any reason to wrap the DbContext in a unit of work class.