← ClaudeAtlas

forge-adaptlisted

Analyse the current project and recommend the forge-kit components that fit it - subagents, skills, commands, and hooks - grouped by type with a per-item reason, then adapt and install the ones you pick (rewritten for your stack, not copy-pasted). Use for first-time setup OR ongoing maintenance ("am I up to date?", "what governance am I missing?"). Secondary modes: "refresh"/"drift" reports which installed components are behind forge-kit (version-marker based) and "refresh <name>" deep-compares and updates one while preserving project adaptation; "forge-adapt contributions" surfaces project-only components worth contributing back; "forge-adapt templates" audits issue templates. Backward-compatible: also triggered by "upgrade-audit".
agigante80/forge-kit · ★ 0 · Data & Documents · score 62
Install: claude install-skill agigante80/forge-kit
<!-- forge-adapt-version: 7 --> # forge-adapt Analyse this project, recommend the forge-kit components that fit it, and install the ones you pick - each rewritten for your stack instead of copy-pasted. The dialogue mirrors a recommender: a short project profile, then the best one or two components per category, each with a one-line reason. Nothing is written until you choose. ## When to use - "run forge-adapt" / "adapt forge-kit to this project" - "what governance is this project missing?" / "suggest forge-kit components" - "am I up to date?" / "run upgrade-audit" (backward-compatible) - "forge-adapt contributions" - contribution-surfacing mode (secondary) - "forge-adapt templates" - issue-template audit mode (secondary) Focus a single category by naming it: "forge-adapt skills", "forge-adapt hooks", etc. --- ## The core flow Three steps the user sees: **Analyze -> Recommend -> Install**. Keep it clean - do not narrate the setup. Run Setup quietly, then lead with the recommendation. ### Setup (quiet - do not print unless something needs the user) **S1. Self-update check.** Compare this skill against the forge-kit remote; auto-update silently when behind. Only print something if an update was applied or failed. ```bash CURRENT_SHA=$(git hash-object "${CLAUDE_SKILL_DIR}/SKILL.md" 2>/dev/null) REMOTE_JSON=$(gh api repos/agigante80/forge-kit/contents/plugins/forge-kit-adapt/skills/adapt/SKILL.md 2>/dev/null) REMOTE_SHA=$(echo "$REMOTE_JSON" | jq -r '.sha // empty' 2>/d