How Neil Kakkar Uses Claude Code for Development Workflow Automation

Neil Kakkar shares specific workflow improvements using Claude Code after joining Tano. He transitioned from manually handling pull requests to automating the process with a custom Claude Code skill.

Automating Pull Request Creation

Kakkar created a /git-pr skill that handles staging changes, writing commit messages, crafting PR descriptions, pushing, and creating PRs on GitHub. The skill reads the full diff and generates more thorough descriptions than manual writing. This eliminated the context switch between coding and describing code.

Optimizing Development Server Performance

He switched the build system to SWC, reducing server restart times from about a minute to under a second. This eliminated the wait time that previously broke focus during context switches.

Automating UI Verification

Kakkar uses Claude Code's preview feature to let the agent verify UI changes instead of manually checking every change. He wired this into his workflow so a change isn't considered "done" until the agent has verified the UI itself. This allows agents to catch their own mistakes and run longer without oversight.

Parallel Development Setup

To handle multiple simultaneous worktrees without port conflicts, Kakkar built a system that assigns unique port ranges to each worktree. This allows running multiple previews simultaneously - he went from being overwhelmed by two parallel branches to running five worktrees at once.

His workflow now involves firing off multiple agents on separate worktrees, each building different features, with agents verifying their own UI changes. He focuses on planning and only steps in for final code review.