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.
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.
curl -O https://raw.githubusercontent.com/heyitsnoah/claudesidian/main/.agents/skills/pull-request/SKILL.mdgit clone --depth 1 https://github.com/heyitsnoah/claudesidianWrote 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.
[](https://agentmods.dev/skills/heyitsnoah/claudesidian/pull-request)<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.
<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>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once 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 |
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.
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 statusto user - Show
git diff --stagedfor 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)
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.
- 1mo ago First seen · 185 lines · 49 tokens per session scan A 32044ea0a768
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.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.