Slash Command

Upgrade Project

Update existing project configurations to current best practices with selective component upgrades

Type: Slash Command
Repository: athola/claude-night-market
GitHub stars: 339
License: MIT
Repo last updated: Sep 24, 2026
Source file: plugins/attune/commands/upgrade-project.md

What Upgrade Project is

Upgrade Project is a slash command published in the athola/claude-night-market repository on GitHub, which has about 339 stars. The repository describes itself as: “23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context optimization, research, and multi-LLM delegation. 186 skills, 128 commands, 54 agents.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Upgrade Project gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Upgrade Project

Claude Code

Download upgrade-project.md from the repository.
Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
Run it by typing / followed by its name.

Claude Cowork

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
In Customize → Skills, click +, then upload the ZIP.
Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/attune/commands/upgrade-project.md, shared under the repository's MIT license. Read the full file on GitHub.

Add missing configurations or update existing ones to match current best practices.

When To Use

Use this command when you need to:

Update project tooling to current standards
Add missing configurations to existing project
Upgrade specific components (Makefile, workflows, hooks)
Bring legacy project up to modern standards
Selectively update outdated configurations

When NOT To Use

Avoid this command if:

Starting new project from scratch (use /attune:project-init)
All configurations current and complete
Need full reinitialization (backup and reinitialize)
Custom configurations that shouldn't be standardized

Usage

# Interactive upgrade - shows what's missing
/attune:upgrade-project

# Upgrade specific component
/attune:upgrade-project --component workflows
/attune:upgrade-project --component makefile
/attune:upgrade-project --component pre-commit

What This Command Does

Detects project language and existing configurations
Identifies missing configurations
Offers to add/update specific components
Preserves custom modifications (merge mode)

Workflow

# 1. Detect project and show status
python3 plugins/attune/scripts/project_detector.py .

# 2. Show missing configurations
# Example output:
# Project: my-project (Python)
# ✅ .gitignore present
# ✅ pyproject.toml present
# ⚠️  Makefile outdated (from 2023, current: 2026)
# ❌ .pre-commit-config.yaml missing
# ❌ .github/workflows/typecheck.yml missing

# 3. Ask which to add/update
# Which configurations to upgrade?
#   [x] Add .pre-commit-config.yaml
#   [x] Add .github/workflows/typecheck.yml
#   [ ] Update Makefile (will preserve custom targets)
…

Components

Available components to upgrade:

makefile - Update Makefile with new targets
workflows - Add/update GitHub Actions workflows
pre-commit - Update pre-commit hook configurations
gitignore - Update .gitignore with new patterns
dependencies - Update dependency specifications

Safety Features

Merge mode: Preserves custom modifications when updating
Backup creation: Creates .bak files before overwriting
Diff preview: Shows changes before applying
Selective upgrade: Choose which components to update

Examples

Example 1: Add Missing GitHub Workflows

/attune:upgrade-project --component workflows

Output:

Detecting project type... Python
Checking existing workflows...
  ✅ .github/workflows/test.yml exists
  ❌ .github/workflows/lint.yml missing
  ❌ .github/workflows/typecheck.yml missing

Add missing workflows? [Y/n]: y
✓ Created: .github/workflows/lint.yml
✓ Created: .github/workflows/typecheck.yml

Example 2: Update Outdated Makefile

/attune:upgrade-project --component makefile

Shows diff and asks for confirmation before updating.

Validation After Upgrade

/attune:validate

Check that all configurations are up-to-date.

Related Commands

/attune:project-init - Initialize new project from scratch
/attune:validate - Validate current project setup

Before you install

Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
Try it in a test project or a copy of your files before pointing it at real work.
Pin the version you tested, and review changes before updating.
Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Upgrade Project?

Upgrade Project is a slash command for Claude Code and Claude Cowork from the athola/claude-night-market repository on GitHub. Update existing project configurations to current best practices with selective component upgrades

How do I install Upgrade Project in Claude Code?

Download upgrade-project.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Upgrade Project in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Upgrade Project safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.