Menu
Update project documentation based on new commits and changes in the repository. Use when: user wants to sync docs after project changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Analyze a project repository and add it to the Arkadian documentation registry with standardized structure. Use when: user provides a path to a new project to onboard.
Analyse an Arkadian orchestrator session - read transcripts, logs, and artifacts to understand what happened and suggest improvements. Use when: user wants to debug or review a past session.
Generate validated operational SOPs for Ark ecosystem projects by testing commands before documenting them. Use when: user wants to create or audit SOPs for a project.
Remove a project from the Arkadian documentation registry and delete all associated documentation files. Use when: user wants to deregister a project.
Self-improvement loop for arkadian. Launches arkadian -d with a GitHub issue, polls until done, evaluates per-agent criteria, reads transcripts on failure, improves prompts, deletes worktree, and relaunches. Loops until passing or max iterations.
Debug and investigate fulmine production issues. Downloads logs and SQLite datadir from remote Docker containers, and queries the Boltz PostgreSQL database remotely. Analyzes errors and queries databases for root cause analysis. Use when: (1) investigating fulmine production errors or failures, (2) checking swap/vHTLC/delegate task status in prod, (3) analyzing fulmine logs for recent issues, (4) debugging VTXO or transaction problems on mainnet, (5) inspecting Boltz swap state in PostgreSQL. Triggers on: "fulmine prod", "production logs", "prod errors", "check prod fulmine", "debug fulmine", "fulmine mainnet issue", "boltz db", "boltz prod".
| name | update-project |
| description | Update project documentation based on new commits and changes in the repository. Use when: user wants to sync docs after project changes. |
| allowed-tools | ["Read","Write","Edit","Bash","Glob","Grep"] |
When to use:
--dry-runUser input: A project ID (e.g., arkd) or absolute path, optionally followed by --dry-run.
This skill analyzes new commits in a project repository and updates the documentation accordingly, keeping the Arkadian registry up-to-date.
Parse input:
/ or ~): use as repo location, derive project-id from directory name${ARKADIAN_DIR}/docs/INDEX.md, find matching entry, extract repo path--dry-run flag: analyze but don't modify filesValidate:
docs/projects/<project-id>/)Step 2.1: Get Last Sync Commit
LAST_SYNC_FILE="${ARKADIAN_DIR}/docs/projects/<project-id>/change-log/last-sync.txt"
LAST_SYNC_COMMIT=$(cat "$LAST_SYNC_FILE" | tr -d '[:space:]')
Step 2.2: Analyze Repository Changes
cd <project-repo-path>
git log ${LAST_SYNC_COMMIT}..HEAD --oneline --no-merges
git log ${LAST_SYNC_COMMIT}..HEAD --stat --no-merges
git diff ${LAST_SYNC_COMMIT}..HEAD --name-only
CURRENT_COMMIT=$(git rev-parse HEAD)
Step 2.3: Categorize Changes
Group by: Features Added/Modified/Removed, Configuration Changes, Dependencies, Architecture Changes, Bug Fixes, Documentation.
| Change Type | Target File(s) |
|---|---|
| New capabilities | docs/INDEX.md, system/project_overview.md |
| Dependencies changed | docs/INDEX.md |
| New features | system/project_overview.md |
| New API endpoints | testing/api-reference.md |
| New env variables | testing/usage.md, testing/how_to_run.md |
| New components | system/architecture.md |
| Build/test changes | sop/development-workflow.md |
For each file needing updates:
Size Limits: usage.md 120 lines, architecture.md 700 words, api-reference.md 200 lines/group, project_overview.md 150 lines.
Update: Key Capabilities, Tags, Dependencies, Depended On By, Dependency Graph, Correlation Matrix.
echo "$CURRENT_COMMIT" > ${ARKADIAN_DIR}/docs/projects/<project-id>/change-log/last-sync.txt
Append entry to change-log/SYNC_HISTORY.md with date, commits analyzed, changes made.
git checkout -b feat/docs-update-<project-id>
git add docs/INDEX.md docs/projects/<project-id>/
git commit -m "docs(<project-id>): update documentation for recent changes"
Show: sync summary (previous/current commit, commits analyzed), documentation updates (files modified, features added, breaking changes), and next steps.
For dry-run: show what WOULD change without modifying anything.