/upgrade-project
Update existing project configurations to current best practices with selective component upgrades
$ npx -y skills add athola/claude-night-market --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/upgrade-project
Context preview
What this command does when you run it.
Update existing project configurations to current best practices with selective component upgrades
Command definition
upgrade-project.mdname: upgrade-project
description: "Update existing project configurations to current best practices with selective component upgrades"
Attune Upgrade-Project Command
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
1. **Detects project language** and existing configurations 2. **Identifies missing configurations** 3. **Offers to add/update** specific components 4. **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)
# 4. Apply selected upgrades
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
Read more
name: upgrade-project description: "Update existing project configurations to current best practices with selective component upgrades"
Attune Upgrade-Project Command
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
1. **Detects project language** and existing configurations 2. **Identifies missing configurations** 3. **Offers to add/update** specific components 4. **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) # 4. Apply selected upgrades
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
A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.
Other commands on claude-night-market.
- /aggregate-logs
Generate LEARNINGS.md from skill execution logs.
Open command - /analyze-skill
Analyze skill file complexity metrics and generate modularization recommendations for splitting or progressive loading.
Open command - /bulletproof-skill
Harden skills against rationalization and bypass behaviors
Open command - /context-report
Generate context optimization report for skill directories
Open command - /create-command
Create slash commands with brainstorming and best practices
Open command - /create-hook
Create hooks with brainstorming and security-first design
Open command

