ownyourcode: Command for Claude Code

/own:done

⚠️ PLAN MODE WARNING: Toggle plan mode off before running this command (shift+tab). OwnYourCode commands don't work correctly with plan mode.

Complete a task with gate checks, senior-level code review, and career value extraction.

Overview

This command is run when the user finishes a task or feature. It performs:

1. Gate Checks — 6 Mentorship Gates verification
2. Code Review — FAANG-level feedback on their code
3. Task Completion — Update the dashboard (task done, DoD, phase status)
4. Interview Story — Extract STAR format story (if career_focus allows)
5. Resume Bullet — Draft action-impact bullet (if career_focus allows)

Profile-Aware Behavior:

• Check .claude/ownyourcode-manifest.json for profile.settings.career_focus
• If career_focus = "full-extraction" → Run all phases including 5 and 6
• If career_focus = "tips-only" → Skip Phases 5 and 6
• If career_focus = "none" → Skip Phases 5 and 6, hide CAREER VALUE in summary

---

Execution Flow

Phase 1: Identify Completed Work

Question: "What did you just finish?"

Options:
1. A task from my active spec
   Description: Completing planned work

2. A bug fix
   Description: Fixed something that was broken

3. A feature (not specced)
   Description: Built something new

4. A refactor
   Description: Improved existing code

If from active spec, read the dashboard to understand context:

• Read ownyourcode/dashboard/dashboard-data.js (window.PROJECT)
• Find the active phase (first with status !== "complete") and the relevant task in its tasks[] (match by text/detail, note its id)
• Note what they were building and why (the phase spec / design)

---

Phase 2: Gather Changes

Review what code was written:

# Recent commits
git log --oneline -5

# Files changed
git diff --name-only HEAD~1

# Or if uncommitted
git status

Ask them to point to the key files:

"Which files contain the main implementation?"

Read those files to understand what they built.