UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
A typical usecase where I think of using Workspaces but they are kind of overcomplicated* and sometimes even difficult to set up, is when I am asked by a backend/devops/boss to make a quick fix on a site that have never been involved in: I don't have necessary access rights, accounts set up, codebase - nothing but "can you do it for me?" sounding over my head.

My ideal plan is that I do my changes and hand out a semi-diff stylesheet file.

By semi-diff I mean a file which contains only touched selectors, but those selectors would have be complete - i.e. they'd include also the properties that have not been touched plus the disabled ones commented out rather than removed. This way they could be easily pasted and replace old ones in the source file.

Please let me know if you need a verbose example.

So, assuming that we don't touch the workflow for DevTools Workspaces workflow (around which I have a bunch of complaints), I would see a new option that would allow me to export that "semi-diff" patch file from Workspaces pane.

What is the expected behavior?

What went wrong?
*I believe the setup and mapping step could be totally automated for the user. By overcomplication I also mean that I am never sure how I should go abobut css files when they are not named following a clean `*.css` pattern (try to customize google.com for that matter to see what I mean). DevTools should pick the name the way it likes and can handle.

Did this work before? N/A 

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 24.0 r0