- Go 98.2%
- Makefile 1.3%
- Shell 0.5%
|
|
||
|---|---|---|
| .codex/skills | ||
| .github/workflows | ||
| campaigns | ||
| cmd/jobfinder | ||
| configs | ||
| deploy/local/search | ||
| docker/postgres/init | ||
| docs | ||
| internal | ||
| profiles | ||
| resumes | ||
| testdata | ||
| tools | ||
| .editorconfig | ||
| .gitignore | ||
| AGENTS.md | ||
| docker-compose.validation.yml | ||
| docker-compose.yml | ||
| go.mod | ||
| go.sum | ||
| Makefile | ||
| PLANS.md | ||
| README.md | ||
| ROADMAP.md | ||
JobSearcher
JobSearcher is a local-first AI-assisted job intelligence system.
M00 establishes the engineering foundation. It does not fetch vacancies, evaluate jobs, process resumes, or provide a Web UI.
M01 adds editable configuration, multiple profile records, profile/campaign relationship validation, and the first CLI commands.
M02 adds a local resume registry with source-file hashes, controlled storage, activation, priority, role-family affinity, and immutable version history. Resume understanding remains future scope.
Verify
Prerequisites: Go 1.22 or newer, GNU Make, and ripgrep (rg).
Run the canonical verification entry point:
make verify
The same command runs locally and in CI. It checks repository metadata, formatting, static analysis, tests, and the build.
Private data boundary
Keep real profiles, campaigns, resumes, reports, application history, and other personal material under the local private/ directory. The directory is ignored by version control. Repository examples must remain synthetic and public.
Run the foundation CLI
go run ./cmd/jobfinder --version
The default development version is dev. Release builds may inject a software
version without changing source code:
go build -ldflags "-X github.com/andrey/jobsearcher/internal/buildinfo.Version=0.2.0" -o bin/jobfinder ./cmd/jobfinder
Milestones such as M00, M01, and M02 describe development scope. They are not software-version identifiers.
Read PLANS.md and docs/milestones/M00/user-validation.md for the current development contract and manual validation procedure.
M01 commands are documented in docs/milestones/M01/user-validation.md.
The command contract is also recorded in docs/interfaces/cli.md.