chore: add CI pipeline, badges, CONTRIBUTING and CODE_OF_CONDUCT

Author: baranylcn

.github/workflows/ci.yml

@@ -0,0 +1,26 @@
+name: CI
+
+on:
+  push:
+    branches: ["main"]
+  pull_request:
+    branches: ["main"]
+
+jobs:
+  ci:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+
+      - run: pip install -e ".[dev]"
+      - run: ruff check .
+      - run: pytest -q

CODE_OF_CONDUCT.md

@@ -0,0 +1,27 @@
+# Code of Conduct
+
+## Our Pledge
+
+We are committed to making participation in this project a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity, level of experience, nationality, personal appearance, race, religion, or sexual identity.
+
+## Our Standards
+
+**Expected behaviour:**
+- Be respectful and constructive in all interactions
+- Accept feedback gracefully
+- Focus on what's best for the project and community
+
+**Unacceptable behaviour:**
+- Harassment, insults, or personal attacks
+- Trolling or deliberately disruptive behaviour
+- Publishing others' private information without consent
+
+## Enforcement
+
+Instances of unacceptable behaviour may be reported by opening a [GitHub issue](https://github.com/PracticalMind/graver/issues) or contacting the maintainers directly. All reports will be reviewed and investigated promptly.
+
+Maintainers have the right to remove, edit, or reject contributions that do not align with this Code of Conduct.
+
+## Attribution
+
+Adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1.

CONTRIBUTING.md

@@ -0,0 +1,36 @@
+# Contributing to graver
+
+## Setup
+
+```bash
+git clone https://github.com/PracticalMind/graver
+cd graver
+python -m venv .venv
+source .venv/bin/activate  # Windows: .venv\Scripts\activate
+pip install -e ".[dev]"
+```
+
+## Before submitting
+
+```bash
+ruff check .       # linting
+pytest -q          # tests
+```
+
+Both must pass cleanly.
+
+## Code standards
+
+- Type hints on all functions
+- No commented-out code
+- Docstrings only when the why is non-obvious — method names should be self-explanatory
+
+## Pull requests
+
+- Branch from `main`, name it `type/short-description` (e.g. `feat/export-json`, `fix/version-collision`)
+- One logical change per PR
+- For significant changes, open an issue first to align on approach
+
+## Reporting issues
+
+Use [GitHub Issues](https://github.com/PracticalMind/graver/issues). Include a minimal reproducible example where possible.

README.md

@@ -1,15 +1,20 @@
 # Graver
 
+[![CI](https://github.com/PracticalMind/graver/actions/workflows/ci.yml/badge.svg)](https://github.com/PracticalMind/graver/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/graver)](https://pypi.org/project/graver/)
+[![Python](https://img.shields.io/pypi/pyversions/graver)](https://pypi.org/project/graver/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+
 Git-like version control for your LLM prompts.
 
-Save prompt versions, view history, compare diffs, and roll back — all from Python, with zero external dependencies.
+Save prompt versions, view history, compare diffs, and roll back, all from Python, with zero external dependencies.
 
 ## Why graver?
 
 LLM prompts change constantly. Tracking what changed, when, and which version performed better quickly becomes a mess.
 
 graver solves this:
-- Every change is automatically versioned — v1, v2, v3...
+- Every change is automatically versioned - v1, v2, v3...
 - Roll back to any version instantly
 - Pin a specific version as your main (canonical) prompt
 - See exactly what changed between two versions
@@ -45,7 +50,7 @@ print(p.changes("v1", "v2"))
 
 ## CLI
 
-The `gr` command lets you use graver directly from the terminal — no Python script needed. Useful for quickly saving files, inspecting version history, or integrating into shell scripts and CI/CD pipelines.
+The `gr` command lets you use graver directly from the terminal, no Python script needed. Useful for quickly saving files, inspecting version history, or integrating into shell scripts and CI/CD pipelines.
 
 ```bash
 gr list                          # list all saved prompts
@@ -117,7 +122,7 @@ Returns the full version history of this prompt, ordered from oldest to newest.
 
 ### `set_main(version) -> None`
 
-Marks a specific version as the main (canonical) version. The main version does not change automatically when new versions are saved — only when `set_main()` is called again.
+Marks a specific version as the main (canonical) version. The main version does not change automatically when new versions are saved, only when `set_main()` is called again.
 
 | Parameter | Type | Description |
 |-----------|------|-------------|
@@ -165,7 +170,7 @@ Returns the raw line-by-line difference between two versions as a dict. Use this
 | `v1` | `str` | Base version (e.g. `"v1"`). |
 | `v2` | `str` | Target version (e.g. `"v2"`). |
 
-**Returns:** Dict with keys `added`, `removed`, `unchanged` — each a list of strings.
+**Returns:** Dict with keys `added`, `removed`, `unchanged`, each a list of strings.
 
 ---
 
@@ -238,7 +243,7 @@ Every `Prompt` writes to a `.graver/` folder in your working directory.
 }
 ```
 
-Version numbering is automatic: each `save()` call increments the counter. Versions are never overwritten — only explicitly deleted via `delete_version()`.
+Version numbering is automatic: each `save()` call increments the counter. Versions are never overwritten, only explicitly deleted via `delete_version()`.
 
 ## License