absolute-init
One-time setup for absolute: interview how you want it to behave (output style, autonomy, TDD strictness, spec dir, families) + detect the stack once, then write `.absolute.config.json` (project, committed) and `~/.absolute/config.json` (user defaults + per-project overrides). Every other absolute-* command reads it instead of re-detecting; non-blocking — commands proceed without it and soft-recommend it. Triggers on "absolute init", "set up absolute", "initialize absolute", "configure absolute", "first-time setup", "remember my conventions for this repo".
maddhruv · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add maddhruv/absolute --skill absolute-init技能说明
name: absolute-init
version: 0.5.0
description: >
One-time setup for absolute: interview how you want it to behave (output style,
autonomy, TDD strictness, spec dir, families) + detect the stack once, then write
.absolute.config.json (project, committed) and ~/.absolute/config.json (user
defaults + per-project overrides). Every other absolute-* command reads it instead
of re-detecting; non-blocking — commands proceed without it and soft-recommend it.
Triggers on "absolute init", "set up absolute", "initialize absolute",
"configure absolute", "first-time setup", "remember my conventions for this repo".
category: workflow
tags:
- workflow
- configuration
- init
- setup
- sdlc platforms:
- claude-code
- gemini-cli
- openai-codex
- mcp user-invocable: true argument-hint: "" license: MIT maintainers:
- github: maddhruv
"set up / initialize / configure absolute"). Start your first response with the ⚙️ emoji.
Absolute Init
One-time setup. Detect the project's real conventions, ask a few questions about how you want absolute to behave, then write that to JSON config the other ten commands read on every run. Result: commands stop re-detecting your stack from scratch and respect your preferences (output style, gating, TDD strictness) without being told each time.
This is the only command that writes config. It is non-destructive: an existing config is shown and updated, never blindly overwritten. It never commits.
When to use
- First time using absolute in a repo — gives every command cached conventions + your preferences.
- Conventions changed (new package manager, new test/lint scripts, branch rename) — re-run to refresh.
- You want to change how absolute behaves globally (output style, autonomy) across projects.
Other commands run fine without init — they fall back to on-the-fly detection and emit a one-line suggestion to run it. init just makes them faster and tailored.
Key principles
- Codebase before questions. Detect everything detectable first. Only ask what the repo can't tell you (preferences, ambiguous choices).
- A few questions, not a grill. ~4-6 max, one at a time. This is setup, not design review.
- Non-destructive. Existing config → show it, confirm each change, merge — don't clobber.
- Never auto-commit. Write the project file; tell the user to commit it. (Commit policy itself is not configurable — absolute never commits.)
- Two levels, project wins. Project config is team-shared and authoritative; global is your personal default + per-project overrides.
Step 1 — DETECT
Auto-detect the stack using the Codebase Convention Detection table in
references/work.md (package manager, language/runtime, test runner, linter/formatter,
build, CI, available scripts). Resolve each to the project's own script form
(npm test, make lint) so cached commands match CI — not raw tools.
Read the actual package.json scripts / Makefile targets to fill test, lint,
typecheck, format, build. Detect the default branch with git symbolic-ref --short refs/remotes/origin/HEAD
(fallback main). Anything you can't resolve confidently → leave it out and ask, or omit.
Also detect, from deps and marker files (omit the whole block if nothing is found):
conventions.format— formatter script:package.jsonformat/fmtscripts, aMakefileformattarget,ruff format, orgofmt.conventions.ui— frompackage.jsondeps:framework(react/vue/svelte/none),styling(tailwindcss → tailwind; css-modules; styled-components; else vanilla),iconLibrary(lucide-react, @heroicons/, @phosphor-icons/, react-icons…),componentLib(shadcn marker / @mui/material → mui / @chakra-ui → chakra / none), andtokensPath(a tokens/theme CSS or TS file if one exists). Omit if the repo has no UI deps.conventions.docs—stack+dirviaabsolute-docs's Stack Detection marker-file table (source.config.ts/fumadocs,docusaurus.config.*, Starlight,mkdocs.yml,.vitepress/, Mintlify, else markdown). Omit if no docs are present.
Step 2 — RESOLVE existing config
Before asking anything, check for existing config (precedence below). If found, print a compact summary of current values and ask whether to update (default) or start fresh. Treat existing values as the defaults for the interview so the user can keep them with one keystroke.
Step 3 — INTERVIEW
Use AskUserQuestion for every preference question. Present options as structured choices with descriptions; mark the recommended/default option first with "(Recommended)" in its label. Ask questions one at a time — wait for each answer before advancing.
Questions (skip any the existing config already answers, unless user asked to reconfigure):
Q1 — Output style
question: "Output style?"
header: "Output style"
options:
- label: "normal (Recommended)"
description: "Full prose, explanations — good for onboarding or unfamiliar codebases"
- label: "terse"
description: "Compressed, minimal prose — matches caveman mode"
Q2 — Autonomy
question: "Autonomy level?"
header: "Autonomy"
options:
- label: "gate-all (Recommended)"
description: "Confirm before every change/wave — full control"
- label: "auto-low-risk"
description: "Auto-apply obviously-safe health waves, gate risky ones"
Q3 — TDD strictness
question: "TDD strictness?"
header: "TDD"
options:
- label: "strict (Recommended)"
description: "Test-first, red→green — failing test must exist before any code"
- label: "pragmatic"
description: "Tests required but not strictly written first"
Q4 — Spec / docs output dir
Ask as free text: "Where should spec/work write design docs? (default: docs/plans)". Accept blank to keep default.
Q5 — Relevant families
question: "Which command families do you use?"
header: "Families"
multiSelect: true
option
阅读完整来源 ↗