obsidian-markdown-lint-mcp-server

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.