Skip to content

Add Claude Code session cost to YouTrack PR comment instructions#69

Open
SimonKaran13 wants to merge 1 commit intomainfrom
simon.karan/add-cost-to-youtrack-comment
Open

Add Claude Code session cost to YouTrack PR comment instructions#69
SimonKaran13 wants to merge 1 commit intomainfrom
simon.karan/add-cost-to-youtrack-comment

Conversation

@SimonKaran13
Copy link
Member

Summary

  • Update CLAUDE.md to instruct that the YouTrack comment when creating a PR should also include the Claude Code session cost (obtained via /cost)
  • Updated in both the "YouTrack Ticket Workflow" section and "After Completing Work" step 8

🤖 Generated with Claude Code

@SimonKaran13 SimonKaran13 marked this pull request as ready for review March 20, 2026 13:13
@SimonKaran13 SimonKaran13 requested review from a team and Copilot March 20, 2026 13:13
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates contributor workflow guidance so that YouTrack PR comments include the Claude Code session cost (retrieved via /cost), improving traceability of AI usage costs alongside PR links.

Changes:

  • Update “YouTrack Ticket Workflow” instructions to include session cost in the PR-related YouTrack comment.
  • Update “After Completing Work” step 8 to include running /cost and adding the cost to the YouTrack comment.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

8. **Update YouTrack** — move the ticket to **Review** state and add
a comment with the PR URL.
a comment with the PR URL and the Claude Code session cost (run
`/cost` to obtain it).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe /cost command returns the amount of resources spent on the whole session, not the resources spent on the particular ticket, so the cost might be misleading in context of the ticket

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. The intent is to practice session hygiene — one ticket per session — so the session cost closely reflects the cost of that ticket. For tickets that span multiple sessions, the reported cost should be treated as a lower bound. This keeps things simple while still providing useful cost visibility.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@SimonKaran13 SimonKaran13 force-pushed the simon.karan/add-cost-to-youtrack-comment branch from f4c4a17 to 77ab039 Compare March 24, 2026 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants