| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Add the variable `configPath` to home-manager, to map directly to the
top level configuration of the current user (`./configs/users/$user').
Add a function to generate the mapping for all the templates we need
for the `llm` CLI.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- Install `repomix` via homebrew
- Add `llm-bundle` just command and `readme-gen` template
- Configure just integration in home config
|
| |
|
|
|
|
| |
- Replaces previous generic commit prompt with a structured Conventional Commits format
- Adds detailed instructions for crafting terse descriptions and optional bodies
- Introduces rules for formatting, content organization, and proper focus on effects rather than changes themselves
|
| |
|
|
|
|
|
|
|
|
|
| |
- Migrated prompts from text files to YAML templates in `.config/llm/templates/` directory
- Updated fish shell aliases to use the new template system with `-t` flag instead of reading files
- Enhanced justfile's `llm` target with proper Claude model setup and 1Password integration
- Added `LLM_USER_PATH` environment variable for consistent configuration path
- Fixed PR prompt format to better organize content and remove issue resolution section
- Updated Nix configuration to support the new file structure
The changes standardize our LLM prompt system and make it more maintainable, while improving the setup experience for new users. 🧰
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Add new section in README about LLM tooling installation
- Create prompts directory with templates for commit and PR messages
- Add new llm.nix module with:
- Configuration for prompt file locations
- Fish shell aliases for generating commit and PR messages using Claude 3.5
- Add `llm` recipe in justfile to install llm CLI tool and Anthropic provider
- Integrate LLM module into home-manager configuration
The changes introduce automation for generating high-quality commit messages and PR descriptions using AI, while keeping the prompts configurable and version controlled.
|
| |
|
|
| |
Simplify the configuration as this is not something I currently use.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The dedicated account for backup should be named 'backup', as it's more
generic.
While it's a system account, I still need to be able to log in the host
remotely with sftp, so we give it a UID (991).
The account needs to be able to sftp to tahoe in order to store the
backups from remote hosts. However we don't want this user to get a
shell and be able to browse the host, so we configure sshd to chroot the
user to where the backups are stored.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- add a comment for each ssh-key that is not stored on a yubikey
- simplify the git commit template
- remove some extra config that I don't need
|
| |
|
|
|
| |
Each key is associated to a variable, which let me be more specific
about which key to use depending on the context.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Add a new module to automatically configure the peers for wireguard. The
module needs a configuration file (in `configs/wireguard.toml`) which
lists all the peers, their IP and and their public keys. The secret keys
is encrypted as a secret with agenix.
There's some initial documentation on how to use this setup.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
There's a few things missing (my binaries for the wifi and battery, at a
minimum), but that's fine for now.
|
| | |
|
| |
|
