psenger

Generate git commit messages, PR titles/descriptions, and changelog entries. Analyzes staged changes, enforces Conventional Commits, scans for sensitive content, links tickets (GitHub Issues / Jira), and updates CHANGELOG.md. Triggers on: "commit", "create a PR", "push", "changelog", "release", or when the user is ready to commit or open a pull request.

Provides the audit checklists, severity criteria (blocking/warning/suggestion), and artifact patterns needed to properly review Agent OS profiles and standards. Always invoke this skill before auditing - without it you can only give generic feedback, not structured severity-tagged findings. Invoke when the user pastes a standard and asks if it is good or what is wrong with it; when the user asks to review, audit, validate, or critique an agent-os profile or standard; or when the user mentions "agent-os profile", "agent-os standard", or "my agent-os setup" in a review or validation context.

Scaffolds production-ready directory structures for agentic AI projects using Agent-OS v3 (Builder Methods). Use when the user asks to set up, scaffold, initialize, or restructure a project for agentic development — including mono-repos, single repos, multi-language repos, full-stack, backend, frontend, or middleware projects. Triggers on "scaffold directory", "project structure", "agentic scaffold", "project layout", "initialize AI project", "directory structure", "agent-os setup", "mono-repo layout", "IaC structure".

Converts transcripts, video summaries, meeting notes, brainstorming sessions, strategy documents, and rough notes into polished Obsidian-flavored Markdown. Activates when creating or editing notes in an Obsidian vault, generating front matter, applying callout blocks, structuring knowledge base articles, or producing developer-facing guides. Also triggers on mentions of Obsidian, front matter, callout blocks, vault organisation, or requests for GitHub-compatible Markdown documents.

Exports a single Obsidian vault note and all its linked images into a portable zip or tar.gz archive, preserving vault-root-relative paths so the archive unpacks correctly anywhere. Use only when the user explicitly invokes /export-vault-note.

Create new agent skills from scratch, modify and improve existing skills, and measure skill performance through evaluation and benchmarking. Use when users want to create a skill, write a skill, build a new skill, edit or optimize an existing skill, run evals to test a skill, benchmark skill performance, or optimize a skill's description for better triggering accuracy. Also triggers when users say "turn this into a skill", "make a skill for X", "skill for doing Y", or ask about skill structure, skill format, or SKILL.md files.

Ships completed work in the ai-agent-skills repository. Two phases depending on context: WRAP UP (on a feature branch with committed work — updates CHANGELOG, README, marketplace.json, commits, pushes, creates a PR) and CUT RELEASE (on main after a merge — determines semver bump, updates CHANGELOG version section, tags, pushes, creates a GitHub draft release). Use when the user says "ship this", "I'm done", "create a PR", "cut a release", "tag a release", "wrap this up", or "release it". Always checks GitHub auth first. Load the `conventions` skill for commit and PR formatting rules.

Defines the commit message, branch naming, pull request, and release note conventions for the ai-agent-skills repository. Make sure to load this skill whenever writing a commit message, naming a branch, drafting a PR title or body, or writing CHANGELOG entries in this repo. Use when the user asks "how should I format this commit", "what's the branch naming convention", "how do I write the PR", "what commit type should I use", or before any git commit, PR creation, release note, or CHANGELOG task in this project.

Begins a new piece of work in the ai-agent-skills repository. Two modes: EXISTING ISSUE (user provides a GitHub issue number or URL — fetches it, cuts the correct branch) and NEW ISSUE (user describes what needs doing — classifies as feature or bug, drafts a structured requirement using the repo's issue template, confirms with the user, creates the GitHub issue, then cuts the branch). Always checks GitHub auth first and confirms user identity. Use when the user says "start work on #14", "begin issue", "start a new feature", "I need to build X", "create an issue for Y", or passes a GitHub issue URL. Load the `conventions` skill for branch naming rules.

Install the Catholic theologian persona AND the bundled reference library (saints, popes, Church Fathers, ecumenical councils, the Beatitudes, the Ten Commandments) into the current directory, so that Claude Code behaves as the catholic-advisor skill for every conversation in that directory. Use when someone says "install the Catholic advisor", "set up Catholic mode", "configure the Catholic persona in this vault", "install catholic-advisor at the repo level", or "I want Claude to always respond as a Catholic theologian here". Best run inside an Obsidian vault, a spiritual notes folder, a Scripture study directory, or any personal knowledge base where the user wants all AI assistance to reflect Catholic teaching.

Answer theological questions as a Catholic theologian, apologist, and spiritual advisor, drawing on Catholic dogma, Sacred Scripture (NRSVCE), the Catechism of the Catholic Church, papal encyclicals, the Church Fathers, and Catholic lay authors, with verifiable source links. Use when answering any question about Catholic theology, Catholic doctrine, the Catholic faith, Scripture interpretation, the saints, the sacraments, moral theology, the ecumenical councils, the Beatitudes, the Ten Commandments, or Catholic apologetics. Triggers on phrases like "what does the Catholic Church teach about", "from a Catholic perspective", "explain this theologically", or any direct theological question in a Catholic context.

Coach Catholic adults on how to have effective conversations with children, teenagers, and young adults (ages 4–25) grounded in Catholic moral teaching, the Beatitudes, and the theological and cardinal virtues. Provides age-specific language strategies, Catholic example openers, and guidance on difficult topics including death and resurrection, relationships and chastity, failure, grief, money, and life skills. Use when a parent, teacher, mentor, or any adult asks how to talk to, explain something to, or have a hard conversation with a child, teen, or young adult. Make sure to use this skill whenever someone asks "how do I talk to my kid about", "how should I explain X to a teenager", "I need to have a hard conversation with a young person", or any similar request involving communicating with someone under 25.

Updates CHANGELOG.md by collecting git commits since the last tag, categorising them into Keep a Changelog v1.1.0 sections (Added, Changed, Fixed, etc.), and cutting a new versioned release entry. Called autonomously by the `release` skill. Accepts VERSION and optional DATE arguments. Do not trigger on general conversation — only activate when explicitly called by another skill or invoked directly as /changelog <version> [date].

Completes a release after the release PR has been merged. Verifies the default branch contains the correct version bump, creates and pushes a git tag, then creates a GitHub release using the changelog entry as release notes. Invoked explicitly as /complete-a-release <version> (e.g. /complete-a-release 0.3.0). Must be run after /start-a-release <version> and after the release PR is merged. Do not trigger on general conversation — only activate on an explicit invocation with a version argument.

Opens a release PR for a given version. Validates the environment, cuts a release/v{VERSION} branch from the default branch, bumps package.json, updates CHANGELOG.md via the changelog skill, commits, pushes, and opens a PR to main. Invoked explicitly as /start-a-release <version> (e.g. /start-a-release 0.3.0). Do not trigger on general conversation about releases — only activate on an explicit invocation with a version argument.

Sets up a local git branch to begin work on a GitHub issue: verifies the environment is clean, fetches issue details, assigns the issue to the current user, derives a typed branch name, and creates the branch. Invoked explicitly with `/start-work-on-an-issue <issue-number>` or `/start-work-on-an-issue <github-issue-url>`. Do not trigger on general conversation about issues — only activate on an explicit invocation with a number or URL argument.

Defines the commit message, branch naming, pull request, and release note conventions for the obsidian-markdown-lint-mcp-server repository. Make sure to load this skill whenever writing a commit message, naming a branch, drafting a PR title or body, or writing CHANGELOG entries in this repo. Use when the user asks "how should I format this commit", "what's the branch naming convention", "how do I write the PR", "what commit type should I use", or before any git commit, PR creation, release note, or CHANGELOG task in this project.

Ships completed work in the obsidian-markdown-lint-mcp-server repository. Two phases depending on context: WRAP UP (on a feature branch with committed work, runs the test gates, updates CHANGELOG and README, commits, pushes, opens a draft PR) and CUT RELEASE (on main after a merge, determines the semver bump, bumps package.json, rolls the CHANGELOG version section, tags, pushes, creates a GitHub draft release). Use when the user says "ship this", "I'm done", "create a PR", "cut a release", "tag a release", "wrap this up", or "release it". Always checks GitHub auth first. Load the conventions skill for commit and PR formatting rules.

Begins a new piece of work in the obsidian-markdown-lint-mcp-server repository. Two modes: EXISTING ISSUE (user provides a GitHub issue number or URL, fetches it, cuts the correct branch) and NEW ISSUE (user describes what needs doing, classifies as feature or bug, drafts a structured issue from the repo's issue form, confirms with the user, creates the GitHub issue, then cuts the branch). Always checks GitHub auth first and confirms user identity. Use when the user says "start work on #14", "begin issue", "start a new feature", "I need to build X", "create an issue for Y", or passes a GitHub issue URL. Load the conventions skill for branch naming rules.

Audit a codebase's JWT, refresh token, session cookie, risk-based authentication, and OIDC implementation against RFC 8725, RFC 9700, OWASP cheat sheets, and NIST SP 800-63B-4, producing a tiered scorecard with evidence-backed findings and concrete fixes. Use when the user asks to audit, review, grade, or harden authentication, sessions, JWTs, refresh tokens, login flows, token storage, password reset, or OIDC integration. Make sure to use this skill whenever the user requests a security assessment of authentication or session code, even if they never say the word JWT.