nsheaps/Todo Sync
plugins/todo-sync/skills/todo-sync/SKILL.md
Automatically syncs todos and plans from ~/.claude/ to the current project. Use this skill when asking about todo sync behavior, troubleshooting sync issues, or understanding where todos are stored.
$ install --global
skillsauthnpx skillsauth add nsheaps/ai-mktpl Todo SyncInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 4:18 PM31.3s1 file scanned
SKILL.md
- name:
- Todo Sync
- description:
- Automatically syncs todos and plans from ~/.claude/ to the current project. Use this skill when asking about todo sync behavior, troubleshooting sync issues, or understanding where todos are stored.
Todo Sync Plugin
This plugin automatically synchronizes your todos and plans from the global Claude directory (~/.claude/) to your current project's .claude/ directory.
How It Works
The plugin uses a PostToolUse hook that triggers after every TodoWrite tool call:
- When you create or update todos using TodoWrite, the hook fires
- The sync script finds your session's todo file in
~/.claude/todos/ - It merges the todos into
.claude/todos/in your project - It also syncs any plan files from
~/.claude/plans/to.claude/plans/
File Locations
Source (Global)
- Todos:
~/.claude/todos/{session-id}.json - Plans:
~/.claude/plans/{plan-name}.md
Destination (Project)
- Todos:
.claude/todos/{session-id}.json - Plans:
.claude/plans/{plan-name}.md
Merge Behavior
Todos: When both source and destination files exist, todos are merged by deduplicating on the content field. This prevents duplicate todo entries.
Plans: Plans are copied if the source is newer than the destination or if the destination doesn't exist.
Troubleshooting
Todos not syncing
- Check if
~/.claude/todos/contains files for your session - Verify the plugin is enabled: look for it in
/pluginscommand output - Check hook execution with
claude --debug
Permission errors
The script creates directories automatically. If you see permission errors:
- Ensure you have write access to your project directory
- Check that
.claude/isn't gitignored with restrictive permissions
Empty todo files
Files containing only [] (empty arrays) are skipped during sync to avoid cluttering the project.
Integration with Git
The plugin automatically adds patterns to ~/.config/git/ignore (the global gitignore) for .claude/todos/ and .claude/plans/ directories. This prevents synced files from being committed in any project by default.
If you want to track todos in version control for a specific project, add explicit !.claude/todos/ pattern to that project's .gitignore.
Manual Sync
The sync happens automatically on TodoWrite. If you need to manually trigger it, simply update your todos:
TodoWrite: [your todos here]
The hook will fire and sync will occur.
Related Skills
nsheaps/github-app-session-env
tools
VerifiedTrustedCommunity
Manually reproduce what the github-app plugin's SessionStart hook does to make a GitHub App installation token usable in the current session — materialize the PEM, generate the token, isolate GH_CONFIG_DIR, write the runtime env file, and wire CLAUDE_ENV_FILE so every Bash call sees GH_TOKEN/GITHUB_TOKEN. Use when the hook did not run, the token is missing from the environment, or a shell/teammate needs the token wired up by hand. <example>GH_TOKEN isn't set even though github-app is configured</example> <example>the github-app SessionStart hook didn't run, set up the token manually</example> <example>wire the github app token into CLAUDE_ENV_FILE</example> <example>gh keeps falling back to the wrong account, isolate GH_CONFIG_DIR</example>
3SKILL.mdUpdated Jun 9, 2026
nsheaps/github-app-git-identity
tools
VerifiedTrustedCommunity
Manually configure the GitHub App bot git identity the way the github-app plugin's SessionStart hook does — resolve the app slug and bot user ID, build the <slug>[bot] name and noreply email, set GIT_AUTHOR_*/GIT_COMMITTER_* env vars, and write an isolated GIT_CONFIG_GLOBAL with the gh auth git-credential helper. Use when commits are attributed to the wrong account, "Author identity unknown" appears, or git identity must be set up by hand. <example>my commits are showing up as the handler, not the bot</example> <example>git says Author identity unknown after the github-app hook ran</example> <example>configure the github app bot git identity manually</example> <example>set up the gh credential helper for git push</example>
3SKILL.mdUpdated Jun 9, 2026
nsheaps/spec-management
tools
VerifiedTrustedCommunity
Manages spec files for requirements capture and validation
3SKILL.mdUpdated Jun 7, 2026
nsheaps/plugins/bash-command-rejection/skills/bash-chaining-alternatives
tools
VerifiedTrustedCommunity
# Bash Chaining Alternatives This skill teaches you how to work around the bash command chaining restriction enforced by this plugin. ## Why Chaining is Blocked The `bash-command-rejection` plugin blocks these operators: | Operator | Name | Why Blocked | | -------- | ---------- | ----------------------------------------------------------------------------------- | | `&&` | AND chain | Runs cmd2 only if cmd1 su
3SKILL.mdUpdated Jun 7, 2026