kivgraph: Skill for Claude Code

.claude/skills/opening-pull-requests/SKILL.md

opening-pull-requests is a skill for Claude Code from Luqueee/kivgraph. It costs 71 tokens per session (1,377 once invoked), scanned A, original, Apache-2.0.

A workflow guide for opening or updating a Kivgraph pull request, which is a proposed code change reviewed before it is merged. It covers checks, automated review, feedback, and merge readiness.

In plain words
What is it for?
It helps prepare changes, run relevant tests, push commits, wait for CI and CodeRabbit, address valid findings, and confirm that the pull request can be merged.
Why use it?
It prevents a pull request from being treated as finished before the latest code has passed required checks and review.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Codex.

This is Luqueee/kivgraph's own configuration. It tells Claude Code how to work on kivgraph itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kivgraph configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Luqueee/kivgraph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Luqueee/kivgraph/main/.claude/skills/opening-pull-requests/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Luqueee/kivgraph

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for opening-pull-requests

README.md
[![agentmods](https://agentmods.dev/badge/skills/luqueee/kivgraph/opening-pull-requests/github.svg)](https://agentmods.dev/skills/luqueee/kivgraph/opening-pull-requests)
Your own site
<a href="https://agentmods.dev/skills/luqueee/kivgraph/opening-pull-requests"><img src="https://agentmods.dev/badge/skills/luqueee/kivgraph/opening-pull-requests/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for opening-pull-requests

Your own site · 80×15
<a href="https://agentmods.dev/skills/luqueee/kivgraph/opening-pull-requests"><img src="https://agentmods.dev/badge/skills/luqueee/kivgraph/opening-pull-requests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,377 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.01377
Opus 5.5 $0.00028 $0.00551
Sonnet 5.5 $0.00014 $0.00275
Haiku 4.5 $0.00007 $0.00138

Measured 1mo ago against content hash f62a28138efe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

opening-pull-requests scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/opening-pull-requests/SKILL.md · 145 lines

How it starts

The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Opening a Kivgraph pull request

The completion condition

Opening the GitHub page is not completion. A PR is ready only when all of these describe its latest head commit:

  • the intended changes are committed and pushed;
  • the relevant local gates have passed;
  • required GitHub checks have completed successfully;
  • CodeRabbit has completed its review of that head;
  • every still-valid actionable finding has been addressed or explicitly explained;
  • GitHub reports no merge conflict or other known merge blocker.

Every push makes earlier CI and bot conclusions stale. Wait again after each feedback commit.

Branch naming

When creating a new branch, use a conventional type followed by one short, lowercase, kebab-case description. Release branches are the one exception: they retain the dotted SemVer so the branch maps directly to its release tag.

feat/add-python-loader
fix/daemon-path-sync
docs/harden-release-skill
test/cover-registry-publish
ci/update-release-gate
chore/refresh-tool-manifest
release/v1.2.3

Use feat, fix, docs, refactor, test, ci, build, perf, chore, or release as appropriate. Never prefix a branch with the agent, model, client, or automation name, including codex/. Keep the name specific to the change, avoid spaces and ticket-only names, and include a ticket identifier only when it improves traceability, preserving the repository's canonical spelling for that identifier.

Apply this convention only when creating a branch. If an existing PR already uses another name, keep its head branch while updating it; do not rename, delete, or recreate it as a side effect of ordinary PR work.

Before pushing a new branch, check the complete remote head-ref namespace. An existing ancestor or descendant ref also blocks the name, even when the exact name is unused:

branch="$(git symbolic-ref --short HEAD)" || {
  echo "cannot determine current branch" >&2
  exit 1
}
refs="$(git ls-remote --heads origin)" || {
  echo "cannot read remote branch refs from origin" >&2
  exit 1
}
conflict=""
while IFS= read -r line; do
  [ -n "$line" ] || continue
  ref="${line#*refs/heads/}"
  case "$ref" in
    "$branch"|"$branch"/*) conflict="$ref"; break ;;
  esac
  case "$branch" in
    "$ref"|"$ref"/*) conflict="$ref"; break ;;
  esac
done <<<"$refs"
if [ -n "$conflict" ]; then
  echo "remote branch namespace conflict: $conflict" >&2
  exit 1
fi

Read the full file on GitHub · 145 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago Changed · +59 lines f62a28138efe
  2. 2mo ago First seen · 86 lines · 71 tokens per session scan A 5d1827866238

Subscribe to this mod's changes

opening-pull-requests is a skill published in the GitHub repository Luqueee/kivgraph (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 71 tokens to every session and 1,377 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

codestory-grounding

Use when discovering repository structure, tracing relationships, analyzing change impact, or validating CodeStory retrieval or an installed plugin through the CodeStory plugin MCP. Skip only for bounded inspection or editing of named files that does not require those operations.

TheGreenCedar/CodeStory · 52 tokens

code-knowledge-graph

Codebase'i knowledge graph olarak analiz et. Dependency, call graph, hotspot analizi.

vibeeval/vibecosystem · 24 tokens

m1nd-first

Use when investigating a repository, searching for implementation, reviewing changes, working from specs/docs, or preparing a risky code change in an environment where m1nd is available. This doctrine makes m1nd the first investigative layer before grep, glob, or manual file reads, except when the task is pure…

maxkle1nz/m1nd · 78 tokens

memtrace-style-fingerprint

Pull the codebase's empirical style norm from Memtrace and match it when writing or editing source code in an indexed repo. Use when choosing between competing idioms (ternary vs if-else, arrow vs function declaration, const vs let, await vs .then, early-return vs nested-return), matching naming case, or when the user…

syncable-dev/memtrace-public · 111 tokens

memtrace-refactoring-guide

Build a phased, risk-scored refactoring plan from Memtrace complexity, dead-code, bridge, impact analysis, and Cortex decision-memory constraints. Use when the user wants to refactor source code, reduce complexity, clean technical debt, delete dead code, split large functions, extract modules, reorganize code, or…

syncable-dev/memtrace-public · 100 tokens

cartograph

Explore a codebase through Cartograph v2's native RocksDB code graph: intent-aware context, exact/BM25/hybrid search, callers/callees/impact, affected tests, live source, review, freshness, and bounded index administration.

adder-factory/cartograph · 0 tokens