一键导入
justfile
Generate a justfile for the current project based on detected project type and deployment method.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Generate a justfile for the current project based on detected project type and deployment method.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Add a "non-production" environment banner to a Phoenix 1.8 app — a sticky bar at the top of every page that warns developers the app is not production. Adds a config entry for the production host, a reusable function component + helpers in the web Layouts module, and renders the banner in every root layout. Detection is host-based (or Mix-env based) and asks for configuration like the production host. Checks what already exists and only adds missing pieces. Use when the user says "env banner", "environment banner", "dev banner", "staging banner", "non-production bar", "not in production banner", or wants a warning bar shown everywhere except production.
Bootstrap account user management UI and backend in a Phoenix 1.8 app. Adds LiveView for listing, inviting, and removing account members with role-based access control. Builds on top of bootstrap-accounts. Use when the user says "bootstrap user management", "add user management", "account users", "invite users", "member management", "manage account members", or wants to add user invitation and role management to an account-scoped Phoenix app.
Inspect OpenSpec artifacts for gaps, correctness, consistency, and codebase alignment. Dispatches subcommands via `/inspector [subcommand] [args]`. Use when the user says "/inspector review", "inspect change", "audit the spec", "/inspector review-update", "review and fix", "/inspector sync-linear", "/inspector commits", "check commits against specs", "/inspector reconcile", "reconcile specs", "sync specs to code", "/inspector explain", "explain the change", "/inspector mockups", "generate mockups", "wireframe the change", "/inspector flows", "generate flow diagrams", "workflow diagrams", "/inspector review-work", "verify and review", or asks to sanity-check, critique, find gaps, generate UI mockups, process flow diagrams, or verify implementation.
Bootstrap Phoenix Application
Set up and configure GoodIssuesReporter in Elixir/Phoenix applications. Dispatches subcommands via `/goodissues-reporter [subcommand]`. Use when the user says '/goodissues-reporter bootstrap', '/goodissues-reporter help', 'add goodissues reporter', 'setup error reporting', 'add goodissues monitoring', or wants to integrate GoodIssuesReporter into a Phoenix app.
Publish a release by running `just publish`. Use when the user says '/publish', 'publish release', 'cut a release', 'release', 'tag and release', or wants to build, tag, and publish a new version.
| name | justfile |
| description | Generate a justfile for the current project based on detected project type and deployment method. |
Generate a justfile for this project with standard recipes based on the detected project type.
Detect project type by checking for these files (in order):
mix.exs → Elixir/Phoenixpackage.json → Node.jspyproject.toml or requirements.txt → Pythongo.mod → GoCargo.toml → RustDetect deployment method by checking for:
fly.toml → use fly deployDockerfile with no fly.toml → use docker build placeholderpackage.json with deploy script → use that scriptdeploy.sh → use ./deploy.shGenerate justfile with these recipes:
# Start development server
up:
mix phx.server
# Deploy to production
deploy:
fly deploy
# Run tests
test:
mix test
# Run quality checks
check:
mix check
# Compile the project
build:
mix compile
# Clean build artifacts
clean:
mix clean
rm -rf _build deps
# Start development server
up:
npm run dev
# Deploy to production
deploy:
npm run deploy
# Run tests
test:
npm test
# Run linting
check:
npm run lint
# Build the project
build:
npm run build
# Clean build artifacts
clean:
rm -rf node_modules dist build .next
# Start development server
up:
python -m uvicorn main:app --reload
# Deploy to production
deploy:
# TODO: Configure deployment
# Run tests
test:
pytest
# Run linting
check:
ruff check .
# Build the project
build:
pip install -e .
# Clean build artifacts
clean:
rm -rf __pycache__ .pytest_cache .ruff_cache dist build *.egg-info
# Start development server
up:
go run .
# Deploy to production
deploy:
# TODO: Configure deployment
# Run tests
test:
go test ./...
# Run linting
check:
go vet ./...
# Build the project
build:
go build -o bin/app .
# Clean build artifacts
clean:
rm -rf bin
# Start development server
up:
cargo run
# Deploy to production
deploy:
# TODO: Configure deployment
# Run tests
test:
cargo test
# Run linting
check:
cargo clippy
# Build the project
build:
cargo build --release
# Clean build artifacts
clean:
cargo clean
fly.toml exists, always use fly deploy for the deploy recipepackage.json scripts and use the actual script names (e.g., dev, start, serve)mix check alias exists in mix.exs; if not, use mix credo --strict# Project automation recipesWrite the justfile to the project root. If a justfile already exists, ask before overwriting.