session:post
Productivitysession:post is an Agent Skill for productivity published in the kagenti/kagenti repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Post Claude Code session stats to a GitHub PR or issue comment
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/kagenti/kagenti/blob/HEAD/.claude/skills/session:post/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/session-post, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
flowchart TD
START(["/session:post"]) --> DETECT["Detect session & PR"]
DETECT --> STATS["--phase stats"]:::phase
STATS --> MERMAID["--phase mermaid"]:::phase
MERMAID --> COMMENT["--phase comment"]:::phase
COMMENT --> SUMMARY["--phase summary"]:::phase
SUMMARY --> DONE([Posted])
classDef phase fill:#2196F3,stroke:#333,color:white
Follow this diagram as the workflow.
Post Session Stats
Post the current Claude Code session statistics to a GitHub PR or issue as a formatted comment.
Workflow
Step 1: Detect Session ID
Find the most recent JSONL session file for this project:
# List recent session files
ls -t ~/.claude/projects/*/session_*.jsonl 2>/dev/null | head -5
The session ID is extracted from the JSONL filename (e.g., session_abc123.jsonl -> abc123).
If multiple sessions exist, use the most recent one unless the user specifies a different session.
Step 2: Detect PR Number
Auto-detect the PR from the current git branch:
gh pr list --head "$(git branch --show-current)" --json number --jq '.[0].number'
If no PR is found for the current branch, ask the user:
- Would they like to post to a specific issue instead?
- Provide the issue number with
--target issue --number <N>
Step 3: Detect Repository
Extract the repository owner/name from the git remote:
git remote get-url origin | sed 's/.*github.com[:/]\(.*\)\.git/\1/' | sed 's/.*github.com[:/]\(.*\)/\1/'
Step 4: Run the Full Pipeline
Execute all phases of the analytics pipeline:
python3 .claude/scripts/session-analytics.py \
--session-id <SESSION_ID> \
--target pr \
--number <PR_NUMBER> \
--repo <OWNER/NAME>
This runs the following phases in sequence:
- stats - Parse the JSONL file and compute metrics (tokens, costs, tool usage, duration)
- mermaid - Generate mermaid diagrams (tool distribution pie chart, timeline)
- comment - Format and post the session comment to the PR/issue
- summary - Update the pinned summary comment with aggregated stats
Step 5: Verify
Confirm the comment was posted successfully:
gh pr view <PR_NUMBER> --json comments --jq '.comments[-1].body[:200]'
Parameters
| Parameter | Source | Required |
|---|---|---|
--session-id | Auto-detected from JSONL files | Yes |
--target | pr or issue | Yes (default: pr) |
--number | Auto-detected from branch | Yes |
--repo | Auto-detected from git remote | Yes |
Examples
# Auto-detect everything and post to PR
python3 .claude/scripts/session-analytics.py \
--session-id abc123 --target pr --number 42 --repo kagenti/kagenti
# Post to a specific issue instead
python3 .claude/scripts/session-analytics.py \
--session-id abc123 --target issue --number 100 --repo kagenti/kagenti
Related Skills
session- Router skill for all session analyticssession:summary- Update pinned summary commentsession:extract- Extract analytics to CSV/MD/HTMLsession:dashboard- Generate HTML dashboard