DavidROliverBA/ArchitectKB / .claude/skills/template-changelog
template-changelog
VerifiedGenerate changelog for ArchitectKB template contributions
Skill: Template Changelog
Command: /template-changelog
Model: π‘ Sonnet
Agent: None (direct execution)
Purpose
Compare this vault with the ArchitectKB template repository and generate changelog entries for features that could be contributed back.
When to Use
- Before syncing changes to the template repo
- During quarterly vault reviews
- After implementing significant new features
- To track what's diverged between vaults
Template Repository
Location: ~/Documents/GitHub/ArchitectKB/
GitHub: https://github.com/DavidROliverBA/ArchitectKB
Implementation
Step 1: Compare File Inventories
Compare these directories between vaults:
| Directory | Content Type |
|---|---|
.claude/scripts/ | Python/Shell scripts |
.claude/skills/ | Skill definitions |
.claude/schemas/ | JSON schemas |
.claude/hooks/ | Pre/post hooks |
.claude/rules/ | Reference documentation |
Templates/ | Note templates |
Step 2: Categorise Differences
For each file, determine:
- New - Exists in this vault but not in template
- Modified - Exists in both but content differs
- Removed - Exists in template but not here (rare, usually intentional)
Step 3: Filter for Template-Worthy Changes
A change is template-worthy if:
- β Generic (no BA-specific references)
- β Reusable across organisations
- β Well-documented
- β Tested and working
Exclude:
- β BA-specific integrations (Notion sync with BA databases)
- β Personal workflow preferences
- β Experimental/incomplete features
- β Files containing credentials or internal URLs
Step 4: Generate Changelog Entries
Use Keep a Changelog format:
## [Unreleased]
### Added
- New `/archive-attachments` skill for orphaned attachment cleanup
- `archive-orphan-attachments.py` script with manifest tracking
- New `location.schema.json` for Location entity type
### Changed
- Updated `frontmatter-validator.py` to support seven-pillar ontology
- Enhanced `tag-taxonomy.md` with workstream hierarchy
### Fixed
- Fixed hardcoded paths in scheduled task scripts
Execution Script
Run this comparison:
#!/bin/bash
VAULT=~/Documents/GitHub/BA-DavidOliver-ObsidianVault
TEMPLATE=~/Documents/GitHub/ArchitectKB
echo "=== New in Vault (not in Template) ==="
for dir in .claude/scripts .claude/skills .claude/schemas .claude/hooks .claude/rules; do
echo "--- $dir ---"
comm -23 <(ls "$VAULT/$dir" 2>/dev/null | sort) <(ls "$TEMPLATE/$dir" 2>/dev/null | sort)
done
echo ""
echo "=== Modified (different content) ==="
for dir in .claude/scripts .claude/skills .claude/schemas .claude/hooks .claude/rules; do
for file in "$VAULT/$dir"/*; do
name=$(basename "$file")
if [ -f "$TEMPLATE/$dir/$name" ]; then
if ! diff -q "$file" "$TEMPLATE/$dir/$name" > /dev/null 2>&1; then
echo "$dir/$name"
fi
fi
done
done
Output
Generate a markdown report with:
- Summary stats - New/Modified/Unchanged counts
- Changelog entries - Ready to paste into CHANGELOG.md
- Candidate list - Files recommended for
/template-sync - Exclusions - Files skipped with reasons
Related Skills
/template-candidates- Detailed analysis of what to sync/template-sync- Execute the sync operation
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product β it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product β not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial β a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK β model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER β read BEFORE opening the target file; don't skip because it "looks like a one-liner" β whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) β never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named β don't Read the file). | Stars: 197k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |