Skip to main content

Git workflow: delivery

Implement on the feature branch​

After approving the plan:

Implement the approved plan.

Requirements:
- Follow existing architecture and conventions
- Limit changes to the approved scope
- Preserve backward compatibility
- Validate user-controlled input
- Handle expected failure conditions
- Add or update tests
- Do not modify unrelated files

Review changes before committing​

Inside Claude Code, use:

/diff

You can also review directly through Git:

git status
git diff
git diff --stat

Check for:

  • Unexpected files
  • Unrelated formatting changes
  • Hardcoded credentials or secrets
  • Missing validation
  • Debugging statements
  • Weak error handling
  • Unnecessary dependencies
  • Missing tests
  • Configuration changes

Run project validation​

Use the verification commands defined by the project.

Example:

npm test
npm run lint
npm run build

For a Python project:

python -m pytest
python -m ruff check .
python -m mypy .
Use project-specific commands

The examples above are not universal. Use the commands defined in the repository documentation, package scripts, CI configuration, or CLAUDE.md.

Ask Claude to review the final change​

Review the complete uncommitted diff.

Check for:
- Functional defects
- Edge cases
- Security concerns
- Missing validation
- Test gaps
- Backward compatibility
- Unnecessary complexity
- Changes outside the approved scope

Do not modify files. Return findings by severity.

Claude Code also provides review-oriented commands such as:

/code-review
/security-review

Availability may depend on the installed Claude Code version and enterprise configuration.

Create a focused commit​

Stage only the intended files:

git add path/to/file1 path/to/file2

Review the staged result:

git diff --staged

Commit with a clear message:

git commit -m "feat: add token estimation workflow"

Push the feature branch:

git push -u origin feature/short-description

Pull-request checklist​

Ready for human review

Confirm that the approved scope was followed, validation passed, the diff was reviewed, sensitive data was excluded, and the pull request explains the change, evidence, risks, and rollback approach.