Your first reviewed release

AI can help you build quickly. A repeatable release workflow helps you understand the changes and decide when they are ready to ship. Use this guide with one small change in an existing project.

1. Start with a project

Follow Getting started to import your folder, connect Claude Code and GitHub, and sync the project information. Start the development process and open its preview.

2. Give the agent a bounded task

Choose one clear improvement, such as fixing a form validation message. Describe the expected behavior and ask the agent to explain what it changed and which checks it ran. Use Plan first if you want to review the approach.

For a GitHub issue, use Resolve with agent to prepare a draft prompt. Review the draft before sending it.

3. Review the changes

Open Git and inspect the changed files. A diff shows the lines added and removed. Check that the change matches the task and that unrelated files are not included.

If something is unclear, ask the agent to explain it or make another change. An agent finishing is your cue to review the result.

4. Save a commit

A commit records a version of the work in Git. Use a message describing the change, review what will be included, and commit when you are satisfied. Push to GitHub when you are ready to share or back up that commit.

Use a branch and pull request when you want a separate review step before merging into the project’s main branch. Git and change control explains these concepts.

5. Run and inspect checks

Run the tests or checks configured for your project. Nocturnal’s Scripts view can run existing project commands, and its CI view shows configured GitHub Actions runs.

If a check fails, inspect its job and log details. Ask the agent to investigate, review the follow-up change, then run the checks again. A project without CI needs a workflow configured in GitHub before Nocturnal can show its runs. Continuous integration.

6. Deploy and verify

Use the deployment script and hosting environment configured for your project. Check the run result, then open the deployed application and verify the expected behavior. Running a script, seeing a passing check, and confirming the live application are separate steps.

7. Record the release

Cut a version to draft a readable changelog. Review it, save it, and mark the version deployed after you have verified it is live. Copy the summary for a client or teammate.

Next: Deployment · Versions and changelogs.