It’s only applicable if you are using RW7.
In your RW sidebar, scroll down to Settings and click General. Scroll to the bottom of the page and click Advanced.
You are then presented with a series of check boxes. Disable cache-busting links here, the 5th option down in the site options.
Now instead of Chrome holding tightly onto these CSS and JS files in its cache, it will reload the CSS and JS files each time the page is refreshed.
You can read more about cache busting links here:
However I think there is a bug in how RW handles cache-busting query strings that @dan probably needs to be made aware of. I noticed that if you make changes to a page (like change some content, adjust a theme style setting or add and remove a stack) the changed flag is correctly applied to the page but the query string applied on the cache-busting links does not change on the published website. Therefore Chrome does not see the latest CSS and JS changes (it assumes the CSS and JS has not changed). I would expect the cache-busting links to receive a NEW query string, if a page gets flagged as changed.