nsheaps/restart
plugins/agentic-behavior/skills/restart/SKILL.md
Restart the Claude Code session by gracefully exiting so the launcher loop restarts it. Use when you need to pick up config changes, plugin updates, or env var changes. Requires a launcher script (e.g., run-agent.sh) that restarts Claude after exit.
$ install --global
skillsauthnpx skillsauth add nsheaps/ai-mktpl restartInstall 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: May 6, 2026, 7:09 AM303.5s1 file scanned
SKILL.md
- name:
- restart
- description:
- |
Restart
This skill enables Claude to restart its own session by performing a graceful exit (SIGINT), relying on the launcher script to restart the process.
When to Use This Skill
- After making configuration changes that require a restart (plugin updates, settings changes)
- After environment variable changes that only take effect on session start
- When the handler requests a restart
- When you need a fresh session to pick up new hooks or rules
How It Works
Restart is simply an exit with the expectation that a launcher script will restart Claude:
- Validate git state -- same checks as
/exit(no uncommitted changes, no unpushed commits) - Save continuation state -- optionally write a continuation prompt so the restarted session picks up where you left off
- Send SIGINT -- gracefully exit the session
- Launcher restarts -- the wrapper script (e.g.,
run-agent.sh) detects the exit and starts a new Claude session
Prerequisites
- A launcher script that restarts Claude after exit (e.g., a
while trueloop) - If no launcher is present, restart behaves identically to exit -- the session simply ends
Quick Method
Use the exit script -- restart is just exit with launcher support:
${CLAUDE_PLUGIN_ROOT}/bin/exit.sh
Saving Continuation State
Before restarting, you may want to save state so the new session can resume:
- Write a continuation prompt to
.claude/tmp/continuation-prompt.md - Update
.claude/scratch/tasks.mdwith current progress - Commit any in-progress work
The launcher script or SessionStart hook can then read the continuation prompt on startup.
Difference from Exit
| Aspect | /exit | /restart |
| ------------------ | --------------- | ------------------------ |
| Intent | End the session | Restart with fresh state |
| Mechanism | SIGINT | SIGINT (same) |
| Launcher behavior | Session ends | Launcher restarts Claude |
| State preservation | Not expected | Save continuation prompt |
| Git validation | Required | Required |
See Also
/exit-- graceful session exit without restartrestartskill in the project repo -- may contain project-specific restart procedures
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