Nm Attune Project Init

v1.0.0

Interactive project initialization with git setup, workflows, hooks, and build configuration. project setup, initialization, scaffold, bootstrap, new project.

0· 89·1 current·1 all-time
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description match the actions the skill instructs: detecting language, collecting metadata, rendering templates, initializing git, and running make/test commands. No unrelated services, binaries, or credentials are requested.
Instruction Scope
Instructions focus on repository-local operations (ls, find, git, make, pytest, rendering templates, running a local Python init script). They do read local files (e.g., git config, source files) which is expected for project initialization and are scoped to the project directory. The docs explicitly warn about missing scripts and ask for user confirmation before overwrites.
Install Mechanism
No install spec is provided (instruction-only skill). Nothing is downloaded or written by the skill bundle itself, minimizing install-time risk.
Credentials
The skill requests no environment variables or credentials. It attempts to infer user.name and user.email from git config — reasonable and proportionate for project metadata collection.
Persistence & Privilege
The skill is not always-enabled and is user-invocable. Model invocation is allowed (normal default). Because it can run commands that modify the working directory and git state, grant it only when you intend the agent to perform local repo changes.
Assessment
This skill is coherent with a project-init utility, but it will run filesystem and git commands and expects a local script at plugins/attune/scripts/attune_init.py (which is not included in the skill bundle). Before using it: (1) run it from a safe/clean directory or a disposable branch; (2) back up or commit existing work because files may be created/overwritten; (3) inspect any referenced scripts/templates (plugins/attune/...) to ensure they come from a trusted source; (4) ensure required tools (python3, git, make, pytest) are installed; (5) decline overwrites or use merge mode when unsure. If you want the agent to run autonomously, be aware it can modify your repo — only allow that for trusted projects.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🦞 Clawdis
latestvk97cwzamvf3v6jc00m6vchhb4x84k7kt
89downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Night Market Skill — ported from claude-night-market/attune. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

Table of Contents

Project Initialization Skill

Interactive workflow for initializing new software projects with complete development infrastructure.

Use When

  • Starting a new Python, Rust, or TypeScript project
  • Updating existing project tooling to current standards
  • Need to set up git, GitHub workflows, pre-commit hooks, Makefile
  • Want consistent project structure across team
  • Converting unstructured project to best practices
  • Adding missing configurations to established codebases

Workflow

1. Detect or Select Language

Load modules/language-detection.md

  • Auto-detect from existing files (pyproject.toml, Cargo.toml, package.json)
  • If ambiguous or empty directory, ask user to select
  • Validate language is supported (python, rust, typescript)

2. Collect Project Metadata

Load modules/metadata-collection.md

Gather:

  • Project name (default: directory name)
  • Author name and email
  • Project description
  • Language-specific settings:
    • Python: version (default 3.10)
    • Rust: edition (default 2021)
    • TypeScript: framework (React, Vue, etc.)
  • License type (MIT, Apache, GPL, etc.)

3. Review Existing Files

Check for existing configurations:

ls -la

Verification: Run the command with --help flag to verify availability.

If files exist (Makefile, .gitignore, etc.):

  • Show what would be overwritten
  • Ask for confirmation or selective overwrite
  • Offer merge mode (preserve custom content)

4. Render and Apply Templates

Load modules/template-rendering.md

Run initialization script:

python3 plugins/attune/scripts/attune_init.py \
  --lang {{LANGUAGE}} \
  --name {{PROJECT_NAME}} \
  --author {{AUTHOR}} \
  --email {{EMAIL}} \
  --python-version {{PYTHON_VERSION}} \
  --description {{DESCRIPTION}} \
  --path .

Verification: Run the command with --help flag to verify availability.

5. Initialize Git (if needed)

# Check if git is initialized
if [ ! -d .git ]; then
  git init
  echo "Git repository initialized"
fi

Verification: Run git status to confirm working tree state.

6. Verify Setup

Validate setup:

# Check Makefile targets
make help

# List created files
git status

Verification: Run git status to confirm working tree state.

7. Next Steps

Advise user to:

# Install dependencies and hooks
make dev-setup

# Run tests to verify setup
make test

# See all available commands
make help

Verification: Run pytest -v to verify tests pass.

Error Handling

  • Language detection fails: Ask user to specify --lang
  • Script not found: Guide to plugin installation location
  • Permission denied: Suggest chmod +x on scripts
  • Git conflicts: Offer to stash or commit existing work

Success Criteria

  • All template files created successfully
  • No overwrites without user confirmation
  • Git repository initialized
  • make help shows available targets
  • make test runs without errors (even if no tests yet)

Examples

Example 1: New Python Project

**Verification:** Run `pytest -v` to verify tests pass.
User: /attune:project-init
## Troubleshooting

### Common Issues

**Command not found**
Ensure all dependencies are installed and in PATH

**Permission errors**
Check file permissions and run with appropriate privileges

**Unexpected behavior**
Enable verbose logging with `--verbose` flag

Comments

Loading comments...