sp-friday-sprint-review-rename

Rename completed Claude Code sessions to date-based titles using scheduledTaskId verification.

1|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/mwolff328-stack/WolffClaude --skill sp-friday-sprint-review-rename
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sp-friday-sprint-review-rename
Source: https://github.com/mwolff328-stack/WolffClaude/tree/main/scheduled-tasks/sp-friday-sprint-review-rename
Command: npx skills add https://github.com/mwolff328-stack/WolffClaude --skill sp-friday-sprint-review-rename

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the limitation where Claude Code sessions cannot rename themselves while they are actively running, ensuring your session history remains organized and searchable.

Core Features & Use Cases

  • Automated Session Renaming: Identifies generic session titles created by scheduled tasks and applies a standardized naming convention.
  • Safety Guardrails: Includes logic to verify the scheduledTaskId to prevent the skill from accidentally renaming its own execution session.
  • Use Case: After a weekly automated sprint review finishes, this skill automatically renames the session to SurvivorPulse Sprint Review - YYYY-MM-DD for better project tracking.

Quick Start

Run the sp-friday-sprint-review-rename skill to identify and rename any recently completed sprint review sessions that still have default titles.

Frequently Asked Questions about sp-friday-sprint-review-rename

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically rename Claude Code sessions for sprint reviews?

To automatically rename Claude Code sessions for sprint reviews, you can use a session management skill that identifies generic session titles and applies a standardized date-based naming convention without manual intervention.

Why do my automated Claude Code sessions keep their default generic titles?

Automated Claude Code sessions retain default generic titles because a session cannot rename itself while actively running, requiring an external automated process to apply standardized naming conventions post-execution.

How does session management verify scheduled task IDs before renaming?

Session management verifies scheduled task IDs by checking the specific task ID associated with the completed session, applying safety guardrails to prevent the renaming skill from accidentally targeting its own active execution session.

Can I use session renaming automation for weekly sprint review housekeeping?

Yes, you can use session renaming automation for weekly sprint review housekeeping by targeting completed sessions with generic titles and converting them to a standardized format like Sprint Review - YYYY-MM-DD for better project tracking.

What is the best way to organize completed Claude Code session histories?

The best way to organize completed Claude Code session histories is applying an automated standardized date-based naming convention to generic session titles, improving workspace organization and historical record-keeping without manual intervention.

Are there limitations to renaming sessions while they are actively running?

Yes, a key limitation is that Claude Code sessions cannot rename themselves while actively running, meaning you must use a separate automated skill to verify task IDs and apply descriptive titles after the target session completes.