direct_prompt -> prompt v1 migration

[jerry-reevo]

I just migrated to v1 and replaced direct_prompt with prompt as recommended by the migration guide, however, it seems to produce wildly different behavior, nearly dysfunctional.

It looks like before with direct_prompt, the provided prompt was inserted into the middle of a larger system prompt constructed by claude-code-action and simply moving to prompt overrides the additional context that was being provided.

Critical context such as the PR number, trigger context, author, repository, etc is no longer automatically provided and the agent now tries to review random repos and PRs until it finds one it can successfully access.

Is there a way to provide fairly long prompts while using the built-in PR review prompt? It sounds like using the --system-prompt or --append-system-prompt claude_args might do the trick, but if we have a long multi-line prompt, providing it as a CLI arg is very hard to read and manage.

[ashwin-ant]

You can include the github context in your prompt string like:

prompt: "Prompt text ... ${{ github.repository }}/pulls/${{ github.event.pull_request.number }}" # or similar

[niebloomj]

@ashwin-ant Examples like this should make it clear that you are going to lose all the baked-in features like tracking tickets if you provide a prompt for auto-review https://github.com/anthropics/claude-code-action/blob/main/examples/claude-auto-review.yml

[km-anthropic]

kashyap here, was on educhat core w/ krishnan :)

We just merged #506 in. This enables users to provide track_progres: true in the workflow file to forward to tag mode.

Example workflow here (https://github.com/km-anthropic/claude-code-action/blob/main/.github/workflows/claude-review.yml) but should be a minor change into your existing ones.

[niebloomj]

We have to catch up!

I'll definitely be testing out that new feature.

Are there other baked-in features we lose out on when we provide a prompt that we might want to expose? I thought I saw a few but would have to check again.

[km-anthropic]

Nothing that comes to the top of my head, this is probably the most important one

[vibhor1997a]

@km-anthropic @ashwin-ant will #506 also cover comments over pull requests.

Eg. If i pass this new flag as true along with my prompt for code review which mode will be triggered. I am currently using pr create events and a specific comment string to trigger my code reviews rather than on every synchronize event to save on costs.