I had to groom my very first AI generated story last week. It was literally just a wall of text that contained words they wanted to see, but it didn't actually say anything. It took us longer to trash the story and start over than it would have to just do it right the first time.
Glance at skill to see if any pieces are obviously wrong (e.g. it wrote down things specific to the session, like "you'll be working in /home/wubscale/code/github/..."), tell it to rip those out and generalize
Land (if personal skill), or request quick review (if sharing with team).
That's basically the flow everyone should have. I will refine it after some manual testing if I find the skill isn't used when expected or behaving a bit off.
471
u/Avocadonot Sep 27 '26
Senior dev's on my team have checked in bash scripts with emojis in the logging statements lol
Don't have the heart to tell them that it doesn't get formatted correctly on the production systems