Archive Session Awareness | sessions | ClaudePluginHub

Skill

Community

Archive Session Awareness

0

Description

Suggest archiving completed work when PRs are merged or work is completed. Triggers when user asks to merge a PR ("merge it", "merge the PR"), after successful gh pr merge, or mentions completion ("shipped", "done with X", "merged to main"). Does NOT archive automatically - suggests running /sessions:archive.

Tool Access

This skill is limited to using the following tools:

ReadGlobBash(gh:*)

Skill Content

Archive Session Awareness

This skill detects when session work may be ready for archiving and suggests the appropriate action.

When to Use This Skill

Trigger when:

User asks to merge: "merge it", "merge the PR", "go ahead and merge", "ship it"
After you successfully run gh pr merge
User mentions completion: "PR merged", "shipped", "done with X", "finished"
User references merged state: "merged to main", "closed the issue"

Instructions

If user asks to merge a PR:
- Perform the merge as requested
- On success, continue to step 2
- On failure, help resolve the issue (don't suggest archiving)
Find git root and check if .sessions/index.md exists
If it exists, read it to assess work state
If user provided a PR URL/number (or you just merged one), verify status:
```
gh pr view [URL/number] --json state,mergedAt,title
```
Assess if work appears complete:
- PR merged?
- Related tasks marked done in session notes?
- No obvious follow-up work mentioned?
If work appears complete, suggest archiving:

"PR merged successfully. This session's work looks complete - want me to archive it? Run /sessions:archive to move completed work to the archive."
If there's more work in the session:

"PR merged. I see there's still [X, Y] in the session notes - want to continue with those or archive what's done so far?"

Important

This skill suggests archiving, it does NOT archive automatically
User must explicitly run /sessions:archive to perform the archive
Trigger AFTER merge succeeds, not before
Multiple PRs may be part of one logical session - check context
If .sessions/ doesn't exist, don't suggest archiving

Links

GitHub Stats

0 forks

Updated 4 hours ago

Related Skills

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

From plugin-dev

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

From plugin-dev

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

From plugin-dev