Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub shavakan/claude-marketplace --plugin shavakan-commandsHow this command is triggered — by the user, by Claude, or both
Slash command
/shavakan-commands:docs-updateThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Update Feature Context Update existing feature context files (context.md, tasks.md) to preserve current state before compaction or break point. ## Additional Instructions $ARGUMENTS --- ## Objective Update existing feature context files to preserve current state. Add recent progress and decisions to context.md, mark completed tasks in tasks.md, document next steps for continuation. **Use when:** - Approaching token limit (compaction warning) - Before long pause (end of day/week) - After significant architectural decisions - When switching to different feature --- ## Execution ##...
/dev-docs-updateUpdates dev documentation before context compaction: task status, session context, unfinished work, handoff notes for seamless continuation.
/updateUpdates .claude/context/ Markdown files (progress, structure, tech, etc.) to reflect current project state via git diffs, file checks, and dep scans. Outputs update stats and summary.
/update-planningUpdates planning docs to reflect implementation progress: reconciles tasks, produces status-grouped checklists, summaries, and next steps.
/docs-updateGenerates, updates, and verifies project documentation by detecting project type, building doc queue, and checking against live codebase.
/docs-updateSyncs documentation across README files and wiki articles by locating wiki repo, analyzing main repo changes, interactively confirming updates, and committing to both.
Share bugs, ideas, or general feedback.
Update existing feature context files (context.md, tasks.md) to preserve current state before compaction or break point.
$ARGUMENTS
Update existing feature context files to preserve current state. Add recent progress and decisions to context.md, mark completed tasks in tasks.md, document next steps for continuation.
Use when:
Find existing feature directory in features/[task-name]/. If multiple exist or none found, ask user which feature to update.
Create timestamped backups before modifying:
context.md.backup-[timestamp]tasks.md.backup-[timestamp]Gate: Feature directory located and backups created successfully.
Present what will be updated:
Update feature context files?
□ Update both - context.md + tasks.md
□ Context only - Add progress and decisions
□ Tasks only - Mark completed tasks
□ Review first - Show current state before updating
□ Cancel
Gate: User must confirm which files to update.
For context.md:
For tasks.md:
- [ ] to - [x])Include specific file references and actionable next steps.
Gate: All updates applied successfully with no syntax errors.
Verify updates meet quality standards:
If validation passes, remove backup files. If validation fails, restore from backups.
Report what was updated: files modified, completed tasks count, next steps documented
If any step fails after backups created, restore original files from backups and report error.
/shavakan-commands:docs-save-context - Save context (works without existing files)/shavakan-commands:docs-feature-plan - Create new feature plan from scratch