Help us improve
Share bugs, ideas, or general feedback.
From attune
Validates project structure, git config, build setup, code quality, CI/CD workflows, and best practices; reports issues, score, and recommendations with --path and --verbose options.
npx claudepluginhub athola/claude-night-market --plugin attuneHow this command is triggered — by the user, by Claude, or both
Slash command
/attune:validateThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Attune Validate Command Check project setup against best practices, identify issues, and recommend improvements. ## When To Use Use this command when you need to: - Validate project structure and configurations - Check for missing required files or settings - Identify configuration issues before deployment - Audit project against best practices - Verify setup after initialization or upgrades ## When NOT To Use Avoid this command if: - Just initialized project (likely passing all checks) - Need to fix issues, not just identify them (use upgrade-project) - Looking for code quality issu...
/validate-project-handoffValidates project handoff by step-by-step testing setup instructions, documentation, and workflows in README.md, CONTRIBUTING.md, docs, and config files. Reports issues for current or specified directory.
/project-healthAudits and manages project configuration: permissions, context, docs. Supports full checks, setup (settings.local.json, CLAUDE.md, .gitignore), tidy, capture learnings, presets, restructure.
/package-reviewReviews current Python package for best-practice violations in structure, pyproject.toml, typing, testing, CI/CD, docs, versioning, API design, packaging, security, DX. Reports findings by principle with fixes and health score.
/auditAudits tech stack and sets up one dev tooling bundle per run (formatting, linting, types, tests, observability, git hooks, database), installing/validating/remediating monorepo-aware.
/validateValidates CLI harness for software at given path or GitHub repo against HARNESS.md standards: directory structure, files, Click CLI, core modules, tests, and docs.
/validateValidates a bug bounty finding through a structured 7-question gate and 4-gate checklist, killing weak submissions before report writing.
Share bugs, ideas, or general feedback.
Check project setup against best practices, identify issues, and recommend improvements.
Use this command when you need to:
Avoid this command if:
# Validate current project
/attune:validate
# Validate specific path
/attune:validate --path /path/to/project
# Show detailed report
/attune:validate --verbose
Project Validation Report
========================
Project: my-awesome-project
Language: Python
Path: /home/user/my-awesome-project
Git Configuration
✅ Git repository initialized
✅ .gitignore present (50 patterns)
Build Configuration
✅ pyproject.toml present
✅ Makefile with 15 targets
⚠️ uv.lock is outdated (run: uv sync)
Code Quality
✅ Pre-commit hooks configured (7 hooks)
✅ Ruff configuration present
✅ MyPy strict mode enabled
CI/CD
✅ Test workflow (.github/workflows/test.yml)
✅ Lint workflow (.github/workflows/lint.yml)
❌ Missing: Type check workflow
Project Structure
✅ Source directory: src/my_awesome_project/
✅ Test directory: tests/
✅ README.md present
❌ Missing: LICENSE file
Score: 17/20 (85%)
Recommendations:
1. Add .github/workflows/typecheck.yml (run: /attune:upgrade-project --component workflows)
2. Add LICENSE file (run: Skill(sanctum:license-generation))
3. Update uv.lock (run: make install)
0 - All checks passed1 - Minor issues (warnings only)2 - Major issues (missing required files)/attune:validate
/attune:validate --verbose --suggestions
Includes:
# .github/workflows/validate.yml
name: Project Structure Validation
on: [push, pull_request]
jobs:
validate:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Validate project structure
run: |
python3 plugins/attune/scripts/validate_project.py --strict
/attune:project-init - Initialize new project/attune:upgrade-project - Fix validation issues automatically