New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Moraine Author PR

by eric-tramel in eric-tramel/moraine

Create Moraine pull requests on GitHub. An agent skill from eric-tramel/moraine.

Apache-2.0Auto-check passedDevelopment

Install Moraine Author PR

skills CLI
$ npx skills add eric-tramel/moraine --skill moraine-author-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install eric-tramel/moraine moraine-author-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/eric-tramel/moraine.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/moraine-dev/skills/moraine-author-pr .claude/skills/moraine-author-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
moraine-author-pr
GitHub stars
117
Token cost
~1.7k tokens
SKILL.md length
499 words
Files
2
Skills in repo
19
Repo updated
First seen
Licence
Apache-2.0

At a glance

Create Moraine pull requests on GitHub. An agent skill from eric-tramel/moraine.

  • The branch is ready to open a PR
  • SKILL.md covers Overview, Title Rules, Body Shape and Description, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • The user asks to create

What it does

Moraine Author PR is an agent skill from eric-tramel/moraine. Create Moraine pull requests on GitHub. Use when the branch is ready to open a PR; when the user asks to create, push, or open a PR; after local changes are committed; or when documenting user-facing features, bug fixes, performance optimizations, validation, changelog impact, or operational impact in a PR that follows repository conventions without AI attribution.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Pull requests, Debugging and Changelog and release notes. It works with GitHub. The repository describes itself as: Unified realtime agent trace database & search MCP. The licence is Apache-2.0.

When your agent uses it

  • The branch is ready to open a PR
  • The user asks to create
  • After local changes are committed
  • Documenting user-facing features

Example prompts

  • “/moraine-author-pr”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 3dd8598. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Moraine Author PR loads about 1.7k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 499 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~96
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from eric-tramel/moraine at commit 3dd8598, republished under its Apache-2.0 licence (© eric-tramel). 499 words, ~1,652 tokens.

Download SKILL.mdSave it as .claude/skills/moraine-author-pr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
moraine-author-pr
description
Create Moraine pull requests on GitHub. Use when the branch is ready to open a PR; when the user asks to create, push, or open a PR; after local changes are committed; or when documenting user-facing features, bug fixes, performance optimizations, validation, changelog impact, or operational impact in a PR that follows repository conventions without AI attribution.

Moraine Author PR

Overview

The goal is to create the PR on GitHub, not just draft title and body text in chat. The skill is complete when the PR exists on GitHub and you return its URL.

Always create a ready-for-review PR. Never create a GitHub Draft PR, never pass --draft, never set draft: true, and never emit an isDraft=true PR directive. If the branch is not ready for reviewer attention, stop and explain what remains instead of opening a Draft PR.

Write PR titles and descriptions that are reviewable, evidence-backed, and consistent across agents. Default bodies use Description, Usage, Changelog, and Validation sections. Base the summary on all commits in the branch, not only the latest one.

If the branch is not ready — uncommitted work, failing tests the user expects fixed first, or the user asked only to revise an existing PR description — say what is blocking creation and what remains. Do not pretend a PR was opened.

Title Rules

Use a concise imperative title. Prefer the repository's Conventional-Commit-like style:

text
feat(monitor): add token trend filters
fix(ingest): preserve cursor sqlite session ids
docs: document agent contributor workflows
chore: tighten sandbox cleanup handling

Do not include AI attribution in the title or body. Do not add generated-by footers, co-author trailers for agents, or notes that the PR was written by an AI tool.

Body Shape

Default to these sections:

markdown
## Description

**What.** [One sentence description].

**Why.** [One sentence description].

[Multi-paragraph description]

## Usage

[How users or developers will see this change]

## Changelog

- ...

## Validation

[Narrative description of how this was validated]

Keep sections short when the PR is small. Add focused extra sections only when useful, such as ## Bug Evidence, ## Performance, ## Operational Impact, or ## References.

Description

Open with bold one-line What. and Why. summaries, then expand in prose, bullets, or examples as needed.

State the concrete change in reviewer-facing terms. Mention files or subsystems when that helps review scope. Explain the reason for the change, not only the implementation. Include code, commands, queries, or before/after examples when they make the motivation concrete.

Good:

markdown
## Description

**What.** Adds a repo-local `moraine-dev` plugin with contributor agent skills.

**Why.** Agents were repeating PR body structure differently across sessions; a shared skill gives each agent the same review contract.

- Vendors `$moraine-dev:moraine-start-work`, `$moraine-dev:moraine-author-pr`,
  and `$moraine-dev:moraine-sandbox-qa` in Codex, with `/moraine-start-work`,
  `/moraine-author-pr`, and `/moraine-sandbox-qa` equivalents in Kiro.
- Documents local installation in `docs/development/agent-contributor-workflows.md`.

That makes it easier for reviewers to find behavior, impact, and test evidence.
Show full SKILL.md (210 more words)Show less

Usage

For user-facing features, demonstrate the feature in the PR description. Use the most natural form for the change: CLI commands, config snippets, API calls, screenshots, curl examples, or monitor UI steps.

Examples:

markdown
## Usage

Run the local Codex plugin marketplace from a checkout:

```bash
codex plugin marketplace add .
```

Then enable `moraine-dev` and invoke:

```text
Use $moraine-dev:moraine-author-pr to create this PR on GitHub.
```

Or launch the repository-local Kiro agent:

```bash
kiro-cli --agent moraine-dev
```

Then invoke the same shared skill:

```text
/moraine-author-pr
```
markdown
## Usage

Example config:

```toml
[mcp]
retrieval_scope = "project_only"
```

With this setting, MCP search only returns sessions from the current project.

Skip usage only when the PR is purely internal and no user, operator, or downstream developer action changes. If skipped, say No user-facing usage change.

Changelog

Summarize the externally meaningful change. Use None when there is no release-note-worthy impact.

Good:

markdown
## Changelog

- Adds developer-only PR authoring guidance for Moraine contributor agents.
- No end-user runtime behavior change.

Validation

Write a short narrative that names exact commands and outcomes. Include skipped validation with a reason.

Example:

markdown
## Validation

Validated plugin metadata with `python3 -m json.tool .agents/plugins/marketplace.json` and `quick_validate.py plugins/moraine-dev/skills/moraine-author-pr`. Ran `make docs-build` successfully. Rust tests were not run; change is docs and plugin metadata only.

For stack-facing changes, include sandbox validation details or state why sandbox QA was not run.

Bug Fixes

Bug fix PRs must include specific evidence that the bug was fixed. Provide at least:

  • The failing behavior or reproducer before the change.
  • The root cause in concrete terms.
  • The code path that changed.
  • The command, test, fixture, or manual check that now passes.

Example:

markdown
## Bug Evidence

Before this PR, `cursor_sqlite` records with missing workspace paths produced
empty project filters:

```text
search_sessions(project_only=true) -> 0 results
```

The fix normalizes the workspace path before writing the session row. The new
fixture covers the missing-path case, and `cargo test -p moraine-ingest-core
cursor_sqlite --locked` now passes.

Performance

Performance optimization PRs must include baseline and PR metrics. Include:

  • Hardware or environment when relevant.
  • Dataset or workload size.
  • Command or measurement method.
  • Baseline metric.
  • PR metric.
  • Delta and caveats.

Example:

markdown
## Performance

Workload: 100k normalized events, local ClickHouse, warm cache.

| Metric | Baseline | This PR | Delta |
| --- | ---: | ---: | ---: |
| `search_sessions` p50 | 182 ms | 121 ms | -33.5% |
| `search_sessions` p95 | 441 ms | 286 ms | -35.1% |

Command:

```bash
bash scripts/bench/search-sessions.sh --events 100000 --warm-cache
```

Do not describe a change as a performance improvement without metrics. If metrics are not available, phrase it as a refactor or preparation work instead.

© eric-tramel, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in plugins/moraine-dev/skills/moraine-author-pr of eric-tramel/moraine.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 3dd8598

Compare with similar skills

Moraine Author PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Moraine Author PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Moraine Author PR this skilleric-tramel/moraine117—~1.7kAutomated safety check: PassApache-2.0
Exposed Bug Fix WorkflowJetBrains/Exposed9.3k—~3.8kAutomated safety check: PassApache-2.0
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Issue Fixmono/SkiaSharp5.6k—~5.1kAutomated safety check: PassMIT
Plannotator Release Preparationbacknotprop/plannotator9.3k—~4.6kAutomated safety check: PassApache-2.0
Ansible Pull Request Reviewansible/ansible71k—~570Automated safety check: PassGPL-3.0

Similar skills

  • Exposed Bug Fix Workflow

    JetBrains/Exposed

    Official

    Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.

    9.3k GitHub stars~3.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Issue Fix

    mono/SkiaSharp

    Fix bugs in SkiaSharp C bindings. An agent skill from mono/SkiaSharp.

    5.6k GitHub stars~5.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Plannotator Release Preparation

    backnotprop/plannotator

    Drafts Plannotator release notes with full contributor credit, bumps versions in dependency order, builds, and starts the tag-driven release pipeline, in four reviewed phases.

    9.3k GitHub stars~4.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Ansible Pull Request Review

    ansible/ansible

    Reviews an Ansible pull request by number, following the steps in the project's CLAUDE.md, with early checks for changelog fragments and tests.

    71k GitHub stars~570 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Plane Release Notes Generator

    makeplane/plane

    Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.

    61k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from eric-tramel/moraine

All 19 skills in this repo

  • Moraine Release Publisher

    eric-tramel/moraine

    Cuts and publishes a Moraine release end to end: version bump PR, tag, GitHub release notes, workflow check and PyPI package verification.

    117 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Moraine Release Notes

    eric-tramel/moraine

    Rewrites a moraine GitHub release body into a usage-focused format with install block, what's new, platform table, upgrade notes and one deduplicated changelog.

    117 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Multi-Persona Code Review

    eric-tramel/moraine

    Coordinates a delegated review of a Moraine PR or local change by seven focused reviewer subagents, merges their findings and follows up on the fixes.

    117 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Elegance-Focused Code Review

    eric-tramel/moraine

    Looks at a pull request for the smallest good design, hunting for simplifications and architectural moves that remove whole classes of problems.

    117 GitHub stars~473 tokensUpdated today
    Auto-check passed

  • Idiomatic Code Review

    eric-tramel/moraine

    Reviews a pull request for idiomatic implementation: use of the language, standard library, ecosystem conventions and the repository's own patterns.

    117 GitHub stars~469 tokensUpdated today
    Auto-check passed

  • Code Review Security Review

    eric-tramel/moraine

    Review a PR through the CodeReviewSecurityReview persona. An agent skill from eric-tramel/moraine.

    117 GitHub stars~497 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Moraine Author PR

What does Moraine Author PR do?

Create Moraine pull requests on GitHub. An agent skill from eric-tramel/moraine. Moraine Author PR is an agent skill from eric-tramel/moraine. Create Moraine pull requests on GitHub.

When should I use Moraine Author PR?

Moraine Author PR fits situations like: the branch is ready to open a PR; the user asks to create; after local changes are committed; documenting user-facing features.

How do I install Moraine Author PR in Claude Code?

Run `npx skills add eric-tramel/moraine --skill moraine-author-pr -a claude-code`. Or copy the skill folder (plugins/moraine-dev/skills/moraine-author-pr in eric-tramel/moraine) into .claude/skills/moraine-author-pr in your project. Claude Code loads it when a task matches its description.

How do I install Moraine Author PR in Codex?

Run `npx skills add eric-tramel/moraine --skill moraine-author-pr -a codex`. Or copy the skill folder (plugins/moraine-dev/skills/moraine-author-pr in eric-tramel/moraine) into .agents/skills/moraine-author-pr in your project. Codex loads it when a task matches its description.

Can I use Moraine Author PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add eric-tramel/moraine --skill moraine-author-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/moraine-author-pr, .gemini/skills/moraine-author-pr, .github/skills/moraine-author-pr and .opencode/skills/moraine-author-pr in your project.

What does Moraine Author PR need to run?

SKILL.md names no scripts, command-line tools or credentials: Moraine Author PR is instructions for the agent only. Our summary lists: Python 3.

Does Moraine Author PR access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Moraine Author PR safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Moraine Author PR use?

Moraine Author PR is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Moraine Author PR use?

About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Moraine Author PR?

Skills that share tags, products or a category with Moraine Author PR: Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Issue Fix (mono/SkiaSharp, 5.6k stars) and Plannotator Release Preparation (backnotprop/plannotator, 9.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Moraine Author PR?

eric-tramel (a GitHub user) maintains it in eric-tramel/moraine, which has 117 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 11, 2026.

Source: eric-tramel/moraine on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.