Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
SimonKaran13 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,8 +97,8 @@ style issues; do not manually fix formatting.
full scope before writing any code.
- When starting work on a ticket, move it to **Develop** state using
`update_issue` (set `State` field).
- After creating a PR, move the ticket to **Review** state and add the
PR URL as a comment.
- After creating a PR, move the ticket to **Review** state and add a
comment with the PR URL and the Claude Code session cost (from `/cost`).
## Commit Messages

- Format: `[DBA-XXX] <imperative summary>` (max 72 chars)
Expand Down Expand Up @@ -126,5 +126,6 @@ style issues; do not manually fix formatting.
7. **Commit & PR** — use the `create-pr` skill (stages, commits, pauses
for confirmation, pushes, and opens the PR).
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

@catstrike catstrike Mar 22, 2026

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

@SimonKaran13 SimonKaran13 Mar 23, 2026

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.

9. Never commit directly to `main`.
Loading