Skip to main content
Don’t want to set this up manually? Paste a link to this page into a Devin session and ask it to set everything up for you.
1

Spot the pattern across sessions

Your team has been using the db-migration skill for a few weeks. It handled renaming columns and adding indexes without issue — but the last two sessions crashed mid-migration when they tried to drop a column referenced by other tables.Open each session and look at the failure point. In this case, sessions 3 and 4 both errored at the same step:
You now have a clear signal: the skill has no step for checking foreign key dependencies before destructive operations. Two sessions succeeded because they touched standalone tables; two failed because they didn’t.
2

Start a session with the skill and the session links

Go to app.devin.ai and start a new session. Mention the skill with @skills:db-migration and paste the links to all four sessions — both the successes and the failures. Including successful sessions lets Devin see what the skill does well, not just where it breaks. (From inside any of those sessions, the session menu’s Improve skill entry starts this prompt for you.)What makes this prompt effective:
  • Names the exact failure — “foreign key constraints” instead of “it sometimes fails”
  • Contrasts successes and failures — Devin can diff the session transcripts to see where they diverge
  • Lists concrete fixes while leaving room for Devin to surface issues you missed
3

Review the skill diff

Devin reads all four session transcripts, pinpoints where failures diverged from successes, and proposes targeted edits. The output looks like a changelog for your skill:
Devin saves the updated skill. If something is off, reply in the same session — for example, “Also add a step to notify the #database Slack channel before running destructive migrations.”
4

Verify the fix on a fresh migration

You don’t need to leave your current Devin session. After the skill update is saved, use the same session to launch a standard Devin session that tests the updated skill against the exact scenario that failed before:If this session succeeds, the fix works. If it hits a new edge case (e.g., circular FK references), start another improve-the-skill session with that session link for another round.