obsidian-markdown-lint-mcp-server: Skill for Claude Code

Release

Ships completed work. The skill detects context and runs the right phase:

• On a feature branch with committed work → WRAP UP phase
• On main after a merge → CUT RELEASE phase

For all message formatting, follow the conventions skill.

---

Step 0: Auth and identity (always)

Check for a GitHub MCP server in available tools. If none:

gh auth status

Stop if neither is available: "I need the GitHub MCP server or gh CLI authenticated. Run gh auth login."

Confirm identity with mcp__github__get_me, otherwise:

gh api user --jq '"@\(.login): \(.name)"'

Show the result and ask: "I'll be acting as @username, is that right?" Wait for confirmation.

---

WRAP UP phase

Triggered when on any non-main branch (feature/, fix/, chore/, refactor/, test/) with a clean working tree.

Step 1: Verify state

git branch --show-current     # must not be main
git status --porcelain        # must be empty; all work committed

If the tree is dirty, stop: "You have uncommitted changes. Commit or stash them first."

Step 2: Run the gates

Confirm the change is green before opening a PR (CONTRIBUTING requires it):

npm run build
npm test
npm run eval

npm run snapshot needs a real Chromium; run it if one is available, otherwise note it as not run. If any gate fails, stop and report.

Step 3: Detect what changed

git diff main...HEAD --name-only

Determine:

• New tool or capability (changes in src/tools/, src/create-server.ts, or a new file under src/) → ### Added, feat
• Changed behavior of an existing tool → ### Changed
• Bug fix → ### Fixed, fix
• Security fix (dependency or audit) → ### Security
• Docs or tooling only → may not need a changelog entry; use judgement

Derive the issue number from the branch name (e.g. feature/14-mermaid-theme-option → #14). If none, ask the user.

Step 4: Update admin files

CHANGELOG.md: add a bullet to ## [Unreleased] under the correct subsection, format (see conventions):

- **scope**: what changed and why. ([#N](issue-url))