For a complete beginner flow from install to generated context, start with First Five Minutes With Ackit.
For an existing-repository adoption workflow, use Prepare A Repository For AI Coding Agents.
ackit init --lang en
ackit scan
ackit scan --ci
ackit doctorackit generate --target all --lang enExisting files are skipped. Review every generated file before committing.
ackit task "Add role based authorization checks" --lang enackit scan
ackit redact-check --profile public-release
ackit doctorackit scan --json
ackit scan --ci --json
ackit redact-check --profile public-release --json
ackit doctor --jsonackit report --output .ackit/reports/current.html --jsonackit webui --output .ackit/webui/current.html --jsonackit prompt-pack --output .ackit/prompt-packs/current.md --jsonReview the generated Markdown locally before any future context export. The command does not call a remote provider.
ackit context-export --prompt-pack .ackit/prompt-packs/current.md --approve --output .ackit/context-exports/current.json --jsonThe manifest records local approval only. It does not upload the prompt pack or call a remote provider.
powershell -ExecutionPolicy Bypass -File scripts/verify-release.ps1Push-Location samples/dotnet-minimal-api
dotnet run --project ../../src/AgentContextKit.Cli/AgentContextKit.Cli.csproj -c Release --no-build -- scan
Pop-Location
Push-Location samples/node-tooling
dotnet run --project ../../src/AgentContextKit.Cli/AgentContextKit.Cli.csproj -c Release --no-build -- scan
Pop-LocationSee SAMPLES.md.
See EXAMPLE_WORKFLOWS.md for copy-paste-ready local development, CI, HTML report, Web UI, prompt pack, public release preflight, and sample scanning workflows.