claudesidian: Skill for Claude Code

.agents/skills/pull-request/SKILL.md

pull-request is a skill for Claude Code, Codex from heyitsnoah/claudesidian. It costs 49 tokens per session (1,164 once invoked), scanned A, original, MIT.

An automated pull-request workflow. A pull request is a GitHub proposal to merge changes into a project branch for review.

In plain words
What is it for?
Use it when a finished fix or feature needs to be sent to GitHub for review.
Why use it?
It handles the repeated steps of creating a feature branch, committing changes, pushing them to GitHub, and opening the review request.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents).

This is heyitsnoah/claudesidian's own configuration. It tells Claude Code and Codex how to work on claudesidian 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 claudesidian configures →

About the project

Claudesidian is a preconfigured Obsidian vault structure that lets Claude Code help manage a personal knowledge base as a thinking partner. It is for people who organize notes and other knowledge in Obsidian, with Git-based version control and optional integrations for image analysis and web research. The catalogue add-ons provide Claude Code skills, agents, hooks, and settings for working with this vault.

heyitsnoah/claudesidian · 2,598 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to heyitsnoah/claudesidian. 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/heyitsnoah/claudesidian/main/.agents/skills/pull-request/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/heyitsnoah/claudesidian

Made for: Claude Code, Codex.

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 pull-request

README.md
[![agentmods](https://agentmods.dev/badge/skills/heyitsnoah/claudesidian/pull-request/github.svg)](https://agentmods.dev/skills/heyitsnoah/claudesidian/pull-request)
Your own site
<a href="https://agentmods.dev/skills/heyitsnoah/claudesidian/pull-request"><img src="https://agentmods.dev/badge/skills/heyitsnoah/claudesidian/pull-request/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 pull-request

Your own site · 80×15
<a href="https://agentmods.dev/skills/heyitsnoah/claudesidian/pull-request"><img src="https://agentmods.dev/badge/skills/heyitsnoah/claudesidian/pull-request.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,164 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.00049 $0.01164
Opus 5.5 $0.00020 $0.00466
Sonnet 5.5 $0.00010 $0.00233
Haiku 4.5 $0.00005 $0.00116

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

Security

Grade A, and why

pull-request 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.

.agents/skills/pull-request/SKILL.md · 185 lines

How it starts

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

Pull Request Command

Creates a new feature branch, commits changes, pushes to GitHub, and opens a pull request - all in one command. Perfect for contributing features or fixes.

Task

Automate the entire pull request workflow: create branch, stage changes, commit with descriptive message, push to GitHub, and open PR with proper description.

Process

1. Check Prerequisites

  • Ensure git repository exists
  • Check for uncommitted changes to include
  • Verify GitHub CLI (gh) is available
  • Get current branch as base branch
  • If already on feature branch, ask: "Create PR from current branch?"

2. Create Feature Branch

# Generate branch name from PR title or use provided name
# Sanitize branch name: lowercase, replace spaces with hyphens, remove special chars
branch_name=$(echo "$branch_name" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9-]/-/g' | sed 's/--*/-/g')

# Check if branch already exists
if git show-ref --verify --quiet refs/heads/$branch_name; then
  echo "Branch $branch_name already exists, using alternative name"
  branch_name="${branch_name}-$(date +%s)"
fi

# Format: feature/short-description or fix/issue-name
git checkout -b $branch_name

3. Stage and Review Changes

  • Show git status to user
  • Show git diff --staged for review
  • If no staged changes, stage all changes: git add -A
  • Confirm changes with user before proceeding

4. Commit Changes

  • Analyze changes to create meaningful commit message
  • Use conventional commits format (feat:, fix:, docs:, etc.)
  • Include detailed commit body if changes are complex
git commit -m "feat: add new feature

- Detail 1
- Detail 2

🤖 Generated with Claude Code"

5. Push to GitHub

# Push with upstream tracking
git push -u origin feature/[branch-name]

6. Create Pull Request

Use gh pr create with:

  • Descriptive title
  • Detailed body with:
    • Summary of changes
    • Testing checklist
    • Related issues (if any)
  • Set base branch (usually main/master)

Read the full file on GitHub · 185 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 First seen · 185 lines · 49 tokens per session scan A 32044ea0a768

Subscribe to this mod's changes

pull-request is a skill published in the GitHub repository heyitsnoah/claudesidian (2,598 stars, last pushed 6mo ago), licensed MIT. It adds 49 tokens to every session and 1,164 once invoked, about $0.0002 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-30.