Skip to content
Skills Library
Programming · Automation

ox-cli-pr-header

/ox-cli-pr-header

Emit and paste the SageOx credit line at the TOP of a pull-request description — the human-facing counterpart to the machine `SageOx-Session:` trailer. Run `ox pr header` at PR-creation time; it renders a thin, on-brand, dark/light-aware single line linking the session(s), plan(s), and discussion(s) that produced the change and naming the team. The CLI owns the sanitizer-fragile markup — you never hand-author it. Use when opening a PR for AI coworker work, or when the user says "add the SageOx header", "credit the session on the PR", or "/ox-cli-pr-header".

Repository
ox ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Emit and paste the SageOx credit line at the TOP of a pull-request description — the human-facing counterpart to the machine `SageOx-Session:` trailer. Run `ox pr header` at PR-creation time; it renders a thin, on-brand, dark/light-aware single line linking the session(s), plan(s), and discussion(s) that produced the change and naming the team. The CLI owns the sanitizer-fragile markup — you never hand-author it. Use when opening a PR for AI coworker work, or when the user says "add the SageOx header", "credit the session on the PR", or "/ox-cli-pr-header".

Triggers from the description

add the SageOx headercredit the session on the PR
Original author description

Emit and paste the SageOx credit line at the TOP of a pull-request description — the human-facing counterpart to the machine `SageOx-Session:` trailer. Run `ox pr header` at PR-creation time; it renders a thin, on-brand, dark/light-aware single line linking the session(s), plan(s), and discussion(s) that produced the change and naming the team. The CLI owns the sanitizer-fragile markup — you never hand-author it. Use when opening a PR for AI coworker work, or when the user says "add the SageOx header", "credit the session on the PR", or "/ox-cli-pr-header".

How it works

  1. When nothing is emitted
Original SKILL.md headings · 38 lines, 246 words
SKILL.md preview
---
name: ox-cli-pr-header
description: >-
  Emit and paste the SageOx credit line at the TOP of a pull-request description
  — the human-facing counterpart to the machine `SageOx-Session:` trailer. Run
  `ox pr header` at PR-creation time; it renders a thin, on-brand, dark/light-aware
  single line linking the session(s), plan(s), and discussion(s) that produced the
  change and naming the team. The CLI owns the sanitizer-fragile markup — you never
  hand-author it. Use when opening a PR for AI coworker work, or when the user says
  "add the SageOx header", "credit the session on the PR", or "/ox-cli-pr-header".
---

**Run the command and follow the `guidance` field it returns.** This skill is a
thin relay: the behavioral rules ship in `ox pr header --json`, so every AI
coworker gets them from the live binary — not just the ones that install skills.

```bash
ox pr header --json
```

Add what the PR credits (the current session is auto-linked):

- `--plan pln_…` — a plan you saved this session. Repeatable.
- `--discussion cnv_…` — a recorded discussion the PR came **directly** out of.
  Rare, and never auto-discovered: only you can judge direct relevance. Ids come
  from `ox conversation list`.
- `--session <url|ses_id>` — adds or overrides sessions.
- `--allow-unconfirmed` — accept links that may not resolve yet.

Then write the body via a **file, never a heredoc** — a heredoc mangles the markup:

```bash
ox pr header > body.md
printf '\n' >> body.md
cat description.md >> body.md   # your written summary
# ...keep the SageOx-Session: trailer as the last line...
gh pr create --body-file body.md
```

## When nothing is emitted

The header renders **only** when it can link at least one artifact a reviewer can
open. With no session, plan, or discussion, `ox pr header` prints nothing on
stdout and says why on stderr — a team name alone is not a credit. That is the
correct outcome, not an error: paste nothing and move on.

It also no-ops when `pr_visuals.header` is off (a team or user opt-out). Don't
force a header in that case.

Versions

The database has no other skills named ox-cli-pr-header.

Database snapshot: 13.11.2026 · package version 38b9e91cf5a6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95sageox
    What SageOx is and how to use it in this repository: load team context at session start, record the session, and reach the team's shared knowledge. Read this when you see a .sageox/ directory, when someone mentions SageOx or the ox CLI, or when ox-cli-* skills are referenced but missing.
  • 90ox
    SageOx team context and session recording for AI coworkers. Use when working in a repository that has .sageox/ initialized, when you need team conventions, or when recording coding sessions to a shared ledger.
  • 100component-docs-header
    This skill should be used when the user asks to "add a component header", "add a ComponentHeader to the X docs page", "change the header demo for X", or otherwise discusses the live demo shown at the top of a component's usage page in the `docs/` site. For a whole new docs page,…
  • 100cpp-header-template
    Generate C++ header files following Google Style Guide. Use when creating new header files or asking for a header template.
  • 100descriptions
    Draft or revise a pull-request description. Use when a user asks for a "PR description", "pull request summary", or "change description".
  • 100migrate-header
    Use this when rebuilding an existing website's header as the header block of an AEM Edge Delivery Services project so that it matches the source 1:1 — closed at every width, with every menu open, with the mobile menu open, and while scrolling. Captures the source header with the…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.