Run any Skill in Manus with one click

gh-weld-export

Stars0

Forks0

UpdatedJune 19, 2026 at 16:37

Export the current Claude Code session as a markdown transcript and post it as a comment on a GitHub PR or issue. Reads the session JSONL file from ~/.claude/projects/, uploads a full transcript as a secret Gist, and posts a structured summary comment with deep-link anchors. Use when: posting session context to a PR after merge, saving conversation history, uploading a session transcript to GitHub, documenting what we did, or when the user says 'export context', 'post context to PR/issue', 'export the session', or 'post session to GitHub'.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

WrathZA

WrathZA/github-weld

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name

gh-weld-export

description

gh-weld-export

Export the current session and post it to a GitHub PR or issue as a structured comment with a Gist link.

Workflow

If invoked by another skill (e.g. gh-weld-ship after merge), the caller passes the PR or issue number as context. Use it directly.

If invoked standalone with no number: ask "Which PR or issue number should I post to?"

Steps

Export the session transcript:

python3 .claude/skills/gh-weld-export/scripts/export-session.py --out .weld/tmp/session-export.md

Upload as a secret Gist:

gh gist create --filename "session-export.md" .weld/tmp/session-export.md > .weld/tmp/gist-url.txt

Read .weld/tmp/gist-url.txt with the Read tool to get <gist-url>.

From session memory, identify 5–10 key events. Include an event if it answers "so what?" for a future reader:
- A design or approach decision was made
- An issue was created, closed, or had its state changed
- A blocker was encountered or resolved
- A constraint or non-obvious fact was discovered
- A file was created or significantly restructured (not just edited)
Exclude: read-only exploration, repeated failed attempts, minor formatting/cleanup changes, file reads with no outcome.
For each key event, find its line number in the transcript:
```
grep -n "<distinctive string from event>" .weld/tmp/session-export.md
```
Run each grep as a separate Bash call. If no match, include the entry without a line anchor.
Use the Write tool to write the summary to .weld/tmp/export-summary.md:
```
## Session Summary

- **<event description>** — [line N](<gist-url>#file-session-export-md-LN)
```
The Gist anchor format for session-export.md is #file-session-export-md-L<N>.
Read the first 100 lines of .weld/tmp/session-export.md with the Read tool (limit: 100) as the inline snippet.

Use the Write tool to write the comment body to .weld/tmp/export-comment.md:

## Session Summary

- **<event>** — [line N](<gist-url>#file-session-export-md-LN)
...

---

<first 100 lines of transcript>

---

[Full session context](<gist-url>)

---
*Created with [gh-weld](https://github.com/WrathZA/github-weld)*

Post the comment:

For a PR:

gh pr comment <number> --body-file .weld/tmp/export-comment.md

For an issue:

gh issue comment <number> --body-file .weld/tmp/export-comment.md

Clean up:
```
rm .weld/tmp/session-export.md .weld/tmp/export-comment.md .weld/tmp/export-summary.md
```
If invoked by another skill (caller mode), do not delete .weld/tmp/gist-url.txt — leave it for the caller to read and remove. If invoked standalone, also remove it:
```
rm .weld/tmp/gist-url.txt
```

NEVER

NEVER use --last N except as --last 1 to isolate a single oversized exchange when debugging — it drops session history and defeats the purpose of the export
NEVER override --max-chars above 65536 — the default of 60000 is a practical cap for readability
NEVER run the script from a directory other than the project root — the project key is inferred from $PWD
NEVER batch multiple grep lookups in one Bash call — each event lookup must be a separate call; Claude Code's safety check fires on multi-command calls and interrupts the session mid-flow
NEVER post to an issue when the caller said PR, or vice versa — confirm the type if ambiguous; gh pr comment on an issue number silently succeeds but posts to the wrong thread
NEVER omit the [Full session context](<gist-url>) link from the comment even if the gist upload appeared to partially succeed — a broken anchor is better than a missing one

Errors

Error	Cause	Fix
`No session directory found`	Wrong CWD or project not opened in Claude Code	Run from project root; verify `~/.claude/projects/<key>/` exists
`No session files found`	Session directory empty	Try again after at least one exchange
`No messages found in session`	JSONL exists but has no user/assistant messages	New or interrupted session
`gh gist create` fails	Rate limit, auth, or network error	Post the first 100 lines of the transcript inline with note: "Full transcript unavailable — Gist upload failed"; omit Gist links from the summary

Do NOT load

scripts/ — invoked via Bash only; do not read as context

More from this repository

same repository

gh-weld-adopt

WrathZA/github-weld

Formalizes untracked work into the GitHub loop — reads session context and git state, creates a structured GitHub issue, creates or renames a branch to match repo conventions, commits loose changes, pushes, and exports the session as a Gist comment on the new issue. This is the forward path for same-session work: when you decide to implement something now without filing an issue first, adopt creates the issue + branch + commit in one step (you don't have to use gh-weld-issue then gh-weld-next). Works equally retroactively on ad-hoc work already done, and from any branch including main (moves uncommitted changes or ahead-commits to a new branch). Use when: you're implementing work this session that has no issue yet, you started work without creating an issue first, or when the user says 'adopt this work', 'track what we're building', 'create an issue for what we're doing', 'formalize this branch', 'retroactively track this', 'adopt this cleanup', 'adopt this chore'.

2026-06-240

gh-weld-repo

WrathZA/github-weld

Create a GitHub repo from a local directory via `gh repo create`. Inspects the current directory to infer repo name, language, topics, .gitignore template, license, and description (from README.md when present) — then interviews the user only for what it cannot infer, one question at a time. Shows a full confirm/edit/abort summary before acting. Pushes the local repo to the new remote on confirm — on a fresh repo, bootstraps the scaffold on a branch so the first work lands via PR. Use when: starting a project that needs a GitHub remote, pushing a local directory to GitHub for the first time. Triggers: "create a repo", "push to GitHub", "new GitHub repo", "initialize remote", "set up GitHub".

2026-06-230

gh-weld-ship

WrathZA/github-weld

GitHub shipping loop — wraps your finished work in a PR, squash-merges it, closes the linked issue, exports the session as a Gist, and posts it as a comment. Enriches the linked issue before closing — updates acceptance criteria checkboxes and posts a close-out narrative comment automatically. Does not implement code; you do the work, gh-weld-ship handles everything GitHub. Use when you're ready to open a PR, squash merge, close an issue, or ready to merge and close a finished feature branch.

2026-06-220

gh-weld-activity

WrathZA/github-weld

GitHub activity digest — lists issues and PRs grouped by time window (today, last 3 days, last 7 days, last 30 days). Supports repo-scoped or GitHub-wide views, selected by single keypress. Use when: the user wants a repo overview, activity summary, recent activity digest, or to see what's changed. Trigger phrases: "what's been happening", "activity digest", "repo overview", "recent activity", "what's new".

2026-06-190

gh-weld-next

WrathZA/github-weld

Pick an open GitHub issue to work on, then create a branch and hand off to the user. Lists open issues, lets you select one, reads the full issue details, optionally adds context notes posted as an issue comment, creates a branch, and confirms you're ready to implement. Pair with /gh-weld-ship when work is done. Use when: starting a new piece of work, picking the next issue from the backlog, adding notes or context to an issue before branching, or annotating an issue with decisions before starting work.

2026-06-190

gh-weld-setup

WrathZA/github-weld

Set up a new or existing project end-to-end — scaffold README.md and CLAUDE.md via a guided abstract (tech-agnostic) interview, wire in gh-weld conventions, ensure .gitignore entries, and optionally create a GitHub repo (delegates to gh-weld-repo). Idempotent: re-run to accept, refresh, or refine existing files. Replaces the separate gh-weld-install and gh-weld-init skills. Use when: starting a new repo, onboarding an existing project to gh-weld, scaffolding README/CLAUDE.md, or wiring conventions. Triggers: 'set up this project', 'init this repo', 'scaffold', 'new project setup', 'install gh-weld', 'wire up weld', 'initialize', 'create README', 'new repository'.

2026-06-190

name

gh-weld-export

description

gh-weld-export

Export the current session and post it to a GitHub PR or issue as a structured comment with a Gist link.

Workflow

If invoked by another skill (e.g. gh-weld-ship after merge), the caller passes the PR or issue number as context. Use it directly.

If invoked standalone with no number: ask "Which PR or issue number should I post to?"

Steps

Export the session transcript:

python3 .claude/skills/gh-weld-export/scripts/export-session.py --out .weld/tmp/session-export.md

Upload as a secret Gist:

gh gist create --filename "session-export.md" .weld/tmp/session-export.md > .weld/tmp/gist-url.txt

Read .weld/tmp/gist-url.txt with the Read tool to get <gist-url>.

From session memory, identify 5–10 key events. Include an event if it answers "so what?" for a future reader:
- A design or approach decision was made
- An issue was created, closed, or had its state changed
- A blocker was encountered or resolved
- A constraint or non-obvious fact was discovered
- A file was created or significantly restructured (not just edited)
Exclude: read-only exploration, repeated failed attempts, minor formatting/cleanup changes, file reads with no outcome.
For each key event, find its line number in the transcript:
```
grep -n "<distinctive string from event>" .weld/tmp/session-export.md
```
Run each grep as a separate Bash call. If no match, include the entry without a line anchor.
Use the Write tool to write the summary to .weld/tmp/export-summary.md:
```
## Session Summary

- **<event description>** — [line N](<gist-url>#file-session-export-md-LN)
```
The Gist anchor format for session-export.md is #file-session-export-md-L<N>.
Read the first 100 lines of .weld/tmp/session-export.md with the Read tool (limit: 100) as the inline snippet.

Use the Write tool to write the comment body to .weld/tmp/export-comment.md:

## Session Summary

- **<event>** — [line N](<gist-url>#file-session-export-md-LN)
...

---

<first 100 lines of transcript>

---

[Full session context](<gist-url>)

---
*Created with [gh-weld](https://github.com/WrathZA/github-weld)*

Post the comment:

For a PR:

gh pr comment <number> --body-file .weld/tmp/export-comment.md

For an issue:

gh issue comment <number> --body-file .weld/tmp/export-comment.md

Clean up:
```
rm .weld/tmp/session-export.md .weld/tmp/export-comment.md .weld/tmp/export-summary.md
```
If invoked by another skill (caller mode), do not delete .weld/tmp/gist-url.txt — leave it for the caller to read and remove. If invoked standalone, also remove it:
```
rm .weld/tmp/gist-url.txt
```

NEVER

NEVER use --last N except as --last 1 to isolate a single oversized exchange when debugging — it drops session history and defeats the purpose of the export
NEVER override --max-chars above 65536 — the default of 60000 is a practical cap for readability
NEVER run the script from a directory other than the project root — the project key is inferred from $PWD
NEVER batch multiple grep lookups in one Bash call — each event lookup must be a separate call; Claude Code's safety check fires on multi-command calls and interrupts the session mid-flow
NEVER post to an issue when the caller said PR, or vice versa — confirm the type if ambiguous; gh pr comment on an issue number silently succeeds but posts to the wrong thread
NEVER omit the [Full session context](<gist-url>) link from the comment even if the gist upload appeared to partially succeed — a broken anchor is better than a missing one

Errors

Error	Cause	Fix
`No session directory found`	Wrong CWD or project not opened in Claude Code	Run from project root; verify `~/.claude/projects/<key>/` exists
`No session files found`	Session directory empty	Try again after at least one exchange
`No messages found in session`	JSONL exists but has no user/assistant messages	New or interrupted session
`gh gist create` fails	Rate limit, auth, or network error	Post the first 100 lines of the transcript inline with note: "Full transcript unavailable — Gist upload failed"; omit Gist links from the summary

Do NOT load

scripts/ — invoked via Bash only; do not read as context