From 3a802cbfd07e46cbbbdef10205d49815d0ea76d8 Mon Sep 17 00:00:00 2001
From: Hasan Alp Caferoglu <alp.caferoglu@gmail.com>
Date: Fri, 9 Oct 2026 23:38:44 +0300
Subject: [PATCH 1/3] chore: add Apache-2.0 license, contributing, code of
 conduct and data-handling docs, CI and release workflows

---
 .claude-plugin/marketplace.json     |   6 +-
 .claude-plugin/plugin.json          |  21 ++-
 .codex-plugin/plugin.json           |  38 +++++-
 .cursor-plugin/plugin.json          |  19 ++-
 .github/check-plugin.sh             |  94 +++++++++++++
 .github/workflows/ci.yml            |  19 +++
 .github/workflows/lint-pr-title.yml |  28 ++++
 .github/workflows/release.yml       |  36 +++++
 CODE_OF_CONDUCT.md                  |  83 ++++++++++++
 CONTRIBUTING.md                     |  39 ++++++
 DATA_HANDLING.md                    |  75 +++++++++++
 LICENSE                             | 202 ++++++++++++++++++++++++++++
 NOTICE                              |   4 +
 README.md                           | 117 ++++------------
 install-skills.sh                   |   3 +-
 scripts/datasqrl-agent.sh           |  33 +++--
 scripts/datasqrl-cloud.sh           |   1 +
 17 files changed, 698 insertions(+), 120 deletions(-)
 create mode 100755 .github/check-plugin.sh
 create mode 100644 .github/workflows/ci.yml
 create mode 100644 .github/workflows/lint-pr-title.yml
 create mode 100644 .github/workflows/release.yml
 create mode 100644 CODE_OF_CONDUCT.md
 create mode 100644 CONTRIBUTING.md
 create mode 100644 DATA_HANDLING.md
 create mode 100644 LICENSE
 create mode 100644 NOTICE

diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json
index 1b5e68a..e9b7255 100644
--- a/.claude-plugin/marketplace.json
+++ b/.claude-plugin/marketplace.json
@@ -1,7 +1,11 @@
 {
   "name": "datasqrl",
   "description": "Build DataSQRL data pipelines from your coding agent, using the Dockerized DataSQRL Code Agent.",
-  "owner": { "name": "DataSQRL" },
+  "owner": {
+    "name": "DataSQRL",
+    "email": "contact@datasqrl.com",
+    "url": "https://datasqrl.com"
+  },
   "plugins": [
     {
       "name": "datasqrl",
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
index 0a1d683..2125ef4 100644
--- a/.claude-plugin/plugin.json
+++ b/.claude-plugin/plugin.json
@@ -1,7 +1,22 @@
 {
   "name": "datasqrl",
-  "version": "0.2.0",
+  "displayName": "DataSQRL",
+  "version": "0.3.0",
   "description": "Plan and implement DataSQRL data pipelines with the Dockerized DataSQRL Code Agent.",
-  "author": { "name": "DataSQRL" },
-  "homepage": "https://datasqrl.com"
+  "author": {
+    "name": "DataSQRL",
+    "email": "contact@datasqrl.com",
+    "url": "https://datasqrl.com"
+  },
+  "homepage": "https://datasqrl.com",
+  "repository": "https://github.com/DataSQRL/datasqrl-plugin",
+  "license": "Apache-2.0",
+  "keywords": [
+    "datasqrl",
+    "sqrl",
+    "data-pipelines",
+    "streaming",
+    "flink",
+    "graphql"
+  ]
 }
diff --git a/.codex-plugin/plugin.json b/.codex-plugin/plugin.json
index b4b9fc7..654bd3d 100644
--- a/.codex-plugin/plugin.json
+++ b/.codex-plugin/plugin.json
@@ -1,6 +1,40 @@
 {
   "name": "datasqrl",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "Plan and implement DataSQRL data pipelines with the Dockerized DataSQRL Code Agent.",
-  "skills": "./skills/"
+  "author": {
+    "name": "DataSQRL",
+    "email": "contact@datasqrl.com",
+    "url": "https://datasqrl.com"
+  },
+  "homepage": "https://datasqrl.com",
+  "repository": "https://github.com/DataSQRL/datasqrl-plugin",
+  "license": "Apache-2.0",
+  "keywords": [
+    "datasqrl",
+    "sqrl",
+    "data-pipelines",
+    "streaming",
+    "flink",
+    "graphql"
+  ],
+  "skills": "./skills/",
+  "interface": {
+    "displayName": "DataSQRL",
+    "shortDescription": "Plan, build and deploy DataSQRL data pipelines",
+    "longDescription": "Describe a data pipeline in plain English. The plugin turns it into a requirements document, runs the Dockerized DataSQRL Code Agent to plan it, waits for your review, then implements, compiles, tests and verifies it. Small changes to an existing project go straight to a patch run, and finished projects deploy to DataSQRL Cloud.",
+    "developerName": "DataSQRL",
+    "category": "Developer Tools",
+    "capabilities": [
+      "Interactive",
+      "Read",
+      "Write"
+    ],
+    "websiteURL": "https://datasqrl.com",
+    "defaultPrompt": [
+      "I want a pipeline that ingests our order events and reports daily revenue.",
+      "Plan a DataSQRL pipeline from my requirements document.",
+      "Is my DataSQRL run still going?"
+    ]
+  }
 }
diff --git a/.cursor-plugin/plugin.json b/.cursor-plugin/plugin.json
index 2c68b56..ab76632 100644
--- a/.cursor-plugin/plugin.json
+++ b/.cursor-plugin/plugin.json
@@ -1,6 +1,21 @@
 {
   "name": "datasqrl",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "Plan and implement DataSQRL data pipelines with the Dockerized DataSQRL Code Agent.",
-  "author": { "name": "DataSQRL" }
+  "author": {
+    "name": "DataSQRL",
+    "email": "contact@datasqrl.com"
+  },
+  "homepage": "https://datasqrl.com",
+  "repository": "https://github.com/DataSQRL/datasqrl-plugin",
+  "license": "Apache-2.0",
+  "keywords": [
+    "datasqrl",
+    "sqrl",
+    "data-pipelines",
+    "streaming",
+    "flink",
+    "graphql"
+  ],
+  "skills": "./skills/"
 }
diff --git a/.github/check-plugin.sh b/.github/check-plugin.sh
new file mode 100755
index 0000000..4dcd4c4
--- /dev/null
+++ b/.github/check-plugin.sh
@@ -0,0 +1,94 @@
+#!/bin/bash
+# SPDX-License-Identifier: Apache-2.0
+#
+# Checks that this repository installs as a working plugin. CI runs it on every pull request and
+# before every release; run it locally before opening a pull request.
+#
+# Usage, from the repository root:
+#   .github/check-plugin.sh              # every check
+#   .github/check-plugin.sh --tag 1.2.3  # also require the tag to match the manifest version
+#
+# Needs bash, python3 and, when installed, shellcheck. Without shellcheck the lint step is skipped
+# with a notice; CI always has it.
+
+set -euo pipefail
+
+cd "$(dirname "${BASH_SOURCE[0]}")/.."
+
+TAG=""
+if [ "${1:-}" = "--tag" ]; then
+    TAG="${2:?--tag needs a value such as 1.2.3}"
+fi
+
+failures=0
+fail() {
+    echo "FAIL: $*" >&2
+    failures=$((failures + 1))
+}
+
+# 1. Scripts: real files, executable, valid bash, and clean under shellcheck. A plugin host copies
+#    the plugin into a cache on install, so a symlink would arrive empty and every skill would fail
+#    to find its script.
+scripts=(scripts/datasqrl-agent.sh scripts/datasqrl-cloud.sh install-skills.sh .github/check-plugin.sh)
+for f in "${scripts[@]}"; do
+    if [ ! -e "$f" ]; then fail "$f is missing"; continue; fi
+    [ -L "$f" ] && fail "$f is a symlink; it must be a real file"
+    [ -x "$f" ] || fail "$f is not executable (git update-index --chmod=+x $f)"
+    bash -n "$f" || fail "$f is not valid bash"
+done
+if command -v shellcheck >/dev/null 2>&1; then
+    shellcheck -S error "${scripts[@]}" || fail "shellcheck reported errors"
+else
+    echo "NOTICE: shellcheck is not installed; skipping the lint step." >&2
+fi
+
+# 2. Manifests: each host reads its own, so each must parse, and all must carry one version.
+manifests=(.claude-plugin/marketplace.json .claude-plugin/plugin.json .codex-plugin/plugin.json .cursor-plugin/plugin.json)
+for m in "${manifests[@]}"; do
+    [ -f "$m" ] || { fail "$m is missing"; continue; }
+    python3 -c 'import json,sys; json.load(open(sys.argv[1]))' "$m" || fail "$m is not valid JSON"
+done
+versions=$(python3 - <<'EOF'
+import json
+for m in (".claude-plugin/plugin.json", ".codex-plugin/plugin.json", ".cursor-plugin/plugin.json"):
+    try:
+        print(m, json.load(open(m)).get("version", "<none>"))
+    except Exception:
+        print(m, "<unreadable>")
+EOF
+)
+VERSION=$(echo "$versions" | awk 'NR==1{print $2}')
+if [ "$(echo "$versions" | awk '{print $2}' | sort -u | wc -l | tr -d ' ')" != "1" ]; then
+    fail "the manifests disagree on the version:"$'\n'"$versions"
+fi
+
+# 3. The Claude manifest keeps the default skills/ scan; a skills key would hide every skill it omits.
+python3 -c 'import json,sys; sys.exit("skills" in json.load(open(".claude-plugin/plugin.json")))' \
+    || fail ".claude-plugin/plugin.json declares a skills key, which hides every skill it does not list"
+
+# 4. Skills: every directory has a SKILL.md whose name matches the directory.
+shopt -s nullglob
+skill_dirs=(skills/*/)
+[ "${#skill_dirs[@]}" -ge 1 ] || fail "no skills found under skills/"
+for d in "${skill_dirs[@]}"; do
+    s=$(basename "$d")
+    if [ ! -f "$d/SKILL.md" ]; then fail "skills/$s/SKILL.md is missing"; continue; fi
+    grep -qx "name: $s" "$d/SKILL.md" || fail "skills/$s/SKILL.md has no 'name: $s' line"
+done
+
+# 5. Skills reach users exactly as written, so maintainer notes belong in CONTRIBUTING.md. An HTML
+#    comment is invisible when rendered but is read by the agent as plain text.
+if grep -rn '<!--' skills/; then
+    fail "an HTML comment is in skills/; move maintainer notes to CONTRIBUTING.md"
+fi
+
+# 6. Release only: the tag is the manifest version, plain SemVer with no "v" prefix.
+if [ -n "$TAG" ] && [ "$TAG" != "$VERSION" ]; then
+    fail "tag $TAG does not match the manifest version $VERSION (expected $VERSION)"
+fi
+
+if [ "$failures" -gt 0 ]; then
+    echo "$failures check(s) failed." >&2
+    exit 1
+fi
+echo "All checks passed (version $VERSION, ${#skill_dirs[@]} skills)."
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
new file mode 100644
index 0000000..0780ae1
--- /dev/null
+++ b/.github/workflows/ci.yml
@@ -0,0 +1,19 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  check:
+    name: Check plugin
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+      # ubuntu-latest ships shellcheck, so the lint step always runs here.
+      - run: .github/check-plugin.sh
diff --git a/.github/workflows/lint-pr-title.yml b/.github/workflows/lint-pr-title.yml
new file mode 100644
index 0000000..3f1762e
--- /dev/null
+++ b/.github/workflows/lint-pr-title.yml
@@ -0,0 +1,28 @@
+name: Lint PR Title
+
+on:
+  pull_request_target:
+    types: [opened, reopened, edited, synchronize]
+
+jobs:
+  validate:
+    runs-on: ubuntu-slim
+    permissions:
+      pull-requests: read
+    if: github.actor != 'dependabot[bot]'
+    steps:
+      - uses: amannn/action-semantic-pull-request@v6
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          types: |
+            feat
+            fix
+            chore
+            test
+            docs
+            refactor
+            ci
+            build
+            perf
+            revert
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
new file mode 100644
index 0000000..d172b76
--- /dev/null
+++ b/.github/workflows/release.yml
@@ -0,0 +1,36 @@
+name: Release
+
+# Runs when a release is published on the GitHub Releases page. It checks the plugin, confirms the
+# release tag is the manifest version, and attaches both scripts, so that
+#   https://github.com/DataSQRL/datasqrl-plugin/releases/latest/download/datasqrl-agent.sh
+# always serves the launcher of the newest release.
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: write
+
+jobs:
+  release:
+    name: Attach scripts to the release
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ github.event.release.tag_name }}
+
+      - name: Check the plugin and the tag
+        env:
+          TAG: ${{ github.event.release.tag_name }}
+        run: .github/check-plugin.sh --tag "$TAG"
+
+      - name: Attach the scripts
+        env:
+          GH_TOKEN: ${{ github.token }}
+          TAG: ${{ github.event.release.tag_name }}
+        run: |
+          gh release upload "$TAG" \
+            scripts/datasqrl-agent.sh scripts/datasqrl-cloud.sh --clobber
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 0000000..b98edc7
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [community@datasqrl.com](mailto:community@datasqrl.com). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..52192b2
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,39 @@
+# Contributing
+
+Thanks for helping improve the DataSQRL plugin.
+
+## Issues and pull requests
+
+- **Report a problem** with an issue. Include your coding agent (Claude Code, Codex, Cursor or Copilot), the plugin version, and the output of `datasqrl-agent.sh --check-config`.
+- **Propose a change** with a pull request against `main`. For a larger change, open an issue first.
+- **Title the pull request** with a [Conventional Commits](https://www.conventionalcommits.org) prefix, such as `feat: add a status skill` or `fix: find the launcher on Windows`. CI checks it.
+
+Everyone taking part follows the [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Test a change locally
+
+Install the plugin from your clone:
+
+```
+/plugin marketplace add /absolute/path/to/datasqrl-plugin
+/plugin install datasqrl@datasqrl
+```
+
+Edits to a `SKILL.md` take effect immediately. After editing a manifest, run `/plugin marketplace update datasqrl` and `/reload-plugins`.
+
+Before you open a pull request, run the checks CI runs:
+
+```bash
+.github/check-plugin.sh
+```
+
+## Rules to keep in mind
+
+- Keep files under `scripts/` as real, executable files. Plugin hosts copy the plugin on install, and a symlink arrives empty.
+- Leave the `skills` key out of `.claude-plugin/plugin.json`. With it, Claude Code loads only the skills it lists.
+- Put maintainer notes in this file, not in HTML comments in a skill. Agents read the comments as plain text.
+- `datasqrl-agent.sh` runs the DataSQRL agent's Docker image. If your change makes it use a new option of that image, merge it only after the image with that option is published. Otherwise users get a launcher that calls an option their image does not have.
+
+## License
+
+By contributing, you agree that your contributions are licensed under the [Apache License, Version 2.0](LICENSE).
diff --git a/DATA_HANDLING.md b/DATA_HANDLING.md
new file mode 100644
index 0000000..ae29f89
--- /dev/null
+++ b/DATA_HANDLING.md
@@ -0,0 +1,75 @@
+# Data handling and telemetry
+
+This page states what the DataSQRL plugin reads, where data goes, and what stays on your machine.
+
+## In short
+
+- The plugin has no telemetry of its own. Its skills are instructions for your coding agent, and they send data only through the two scripts in `scripts/`.
+- The DataSQRL Code Agent runs in a Docker container on your machine. It sends your prompts and project code to the model provider you choose, and to nothing else unless you opt in.
+- Telemetry is off by default. With `DATASQRL_TELEMETRY=1`, the run log is uploaded to DataSQRL for troubleshooting.
+- `deploy` and `promote` talk to DataSQRL Cloud, and only when you ask for them.
+
+Your coding agent (Claude Code, Codex, Cursor or Copilot) has its own data policy, which this page does not cover.
+
+## What a run can read and write
+
+`scripts/datasqrl-agent.sh` starts the agent container with these mounts:
+
+| Host path | In the container | Access |
+|-----------|------------------|--------|
+| The git repository around your project | `/workspace` | read-only |
+| Your project directory | `/workspace/<project>` | read-write |
+| Claude credentials, when you use a Claude login instead of an API key | `/root/.claude/.credentials.json` | read-only |
+| Files named by `GOOGLE_APPLICATION_CREDENTIALS`, `AWS_WEB_IDENTITY_TOKEN_FILE`, `AWS_SHARED_CREDENTIALS_FILE`, `AWS_CONFIG_FILE` or `ANTHROPIC_IDENTITY_TOKEN_FILE`, when set | the same path | read-only |
+| gcloud Application Default Credentials, for a Vertex run without `GOOGLE_APPLICATION_CREDENTIALS` | `/root/.config/gcloud/` | read-only |
+
+The project directory is the only place a run can write. A run writes these files there:
+
+- `adr/requirements_<ts>.md` and `adr/plan_<ts>.md`, the requirements and the plan.
+- `AGENTS.md` and `.claude/`, the agent's instructions, its progress trail and its structured run log (`.claude/codeagent_logs.jsonl.bak`).
+- `build/`, the compiler output.
+- `.code_agent_results.json`, the run history.
+- The DataSQRL project files the agent creates or edits.
+
+## Environment variables
+
+The launcher passes variables into the container by name, and only the names on its `PROVIDER_ENV_VARS` list: the model provider credentials and `DATASQRL_TELEMETRY`. A variable that is unset on your host is skipped, and these values never appear in the `docker run` arguments. To pass more, list their names in `DATASQRL_AGENT_PASS_ENV`.
+
+The launcher also sets these in the container itself:
+
+- `MCP_SERVER_URL`, when you set it.
+- `WORKSPACE_DIR`, the project path inside the container.
+- `HOST_WORKSPACE_FOLDER`, the name of your project folder (not its full path).
+- `HOST_MAC_ID`, the MAC address of your machine's first network interface.
+
+The last two label the run log so that runs from one machine and project can be told apart. They stay in the local log unless you opt in to telemetry.
+
+Everything else in your shell stays outside the container.
+
+## Credentials
+
+- **Model provider.** The coding agent inside the container and its reviewing judges both use the credential of the provider you chose, such as `ANTHROPIC_API_KEY`, `FIREWORKS_API_KEY` or an AWS credential for Amazon Bedrock.
+- **Claude login.** Without `ANTHROPIC_API_KEY`, the launcher uses `CLAUDE_CODE_OAUTH_TOKEN`, then `~/.claude/.credentials.json`, then on macOS the Claude Code entry in the Keychain. A token from the variable or the Keychain is written to a temporary file that only your user can read and is mounted read-only. For an attached run the file is deleted when the launcher exits. For a detached run it stays at `${TMPDIR:-/tmp}/datasqrl-agent-creds-<run>.json`, because the container still needs it, and the next run on the same project overwrites it.
+- **AWS profile.** For a Bedrock run or an opted-in log upload, `AWS_PROFILE` is turned into one temporary credential on your host and passed in as variables. `~/.aws` is never mounted.
+- **Pro edition token.** `DATASQRL_PRO_TOKEN` is sent to `api.github.com` to look up its account and to `ghcr.io` for `docker login`. It is passed on stdin and stays outside the container.
+- **DataSQRL Cloud.** `scripts/datasqrl-cloud.sh` signs in with a device-code flow that you approve in a browser. It caches the token in `${XDG_CONFIG_HOME:-~/.config}/datasqrl/credentials.json` with mode `0600`; on Windows NTFS that mode has no effect. `datasqrl-cloud.sh logout` deletes it.
+
+## Network destinations
+
+| Destination | When | What is sent |
+|-------------|------|--------------|
+| Your model provider | Every run | Prompts, the plan, project files the agent reads, tool output |
+| `ghcr.io` | Pulling the agent image | An image pull, and a login for the pro edition |
+| `api.github.com` | Pro edition with `DATASQRL_PRO_TOKEN` | The token, to find its account name |
+| Your MCP server | Only when `MCP_SERVER_URL` is set | What the agent sends to its tools |
+| `s3://datasqrl-debug-logs` | Only with `DATASQRL_TELEMETRY=1` | The run log (see below) |
+| `cloud.datasqrl.com`, or `DATASQRL_BASE_URL` | Only `deploy` and `promote` | Sign-in, and the commit, project and deployment ids of the action you asked for |
+| `api.github.com` or `gh` | Only `resolve-issue` | A request to read the issue you named |
+
+## Telemetry
+
+Telemetry is opt-in and off by default.
+
+When you set `DATASQRL_TELEMETRY=1` and provide AWS credentials, the run log is uploaded at the end of the run to `s3://datasqrl-debug-logs/<mode>/<request-uuid>_logs.jsonl`. DataSQRL uses it to troubleshoot and debug the agent. The log is the structured record of the run: the agent's messages, its tool calls and their output, test and verification results, and the run result. It can therefore contain excerpts of your code, your test data and command output. Every log entry also carries the run mode, your project folder name and your machine's MAC address.
+
+Without `DATASQRL_TELEMETRY=1`, the log stays in your project, whatever AWS credentials are set. With `DATASQRL_TELEMETRY=1` and incomplete AWS credentials, the run logs a warning and keeps the log local.
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..57bc88a
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
diff --git a/NOTICE b/NOTICE
new file mode 100644
index 0000000..96824e1
--- /dev/null
+++ b/NOTICE
@@ -0,0 +1,4 @@
+DataSQRL plugin for coding agents
+Copyright © 2026 DataSQRL (contact@datasqrl.com)
+
+This product includes software developed at DataSQRL (https://datasqrl.com).
diff --git a/README.md b/README.md
index edc69ab..652ac2b 100644
--- a/README.md
+++ b/README.md
@@ -95,13 +95,6 @@ For `deploy` and `promote` only:
 
 ## Install
 
-### Claude Code (Local)
-
-```
-/plugin marketplace add <absolute path to code-agent/datasqrl-plugin>
-/plugin install datasqrl@datasqrl
-```
-
 ### Claude Code
 
 ```
@@ -109,6 +102,8 @@ For `deploy` and `promote` only:
 /plugin install datasqrl@datasqrl
 ```
 
+To install from a local clone instead, pass its absolute path to `marketplace add`.
+
 ### Codex
 
 ```
@@ -130,7 +125,13 @@ git clone https://github.com/DataSQRL/datasqrl-plugin
 ```
 
 That copies the skills into `.github/skills/` and `.agents/skills/`. The skills invoke
-`datasqrl-agent.sh` by name, so it must be on your `PATH` — the installer tells you how.
+`datasqrl-agent.sh` by name, so it must be on your `PATH`. Every release attaches the launcher, and
+this installs the latest one:
+
+```bash
+curl -fsSL https://github.com/DataSQRL/datasqrl-plugin/releases/latest/download/datasqrl-agent.sh \
+  -o /usr/local/bin/datasqrl-agent.sh && chmod +x /usr/local/bin/datasqrl-agent.sh
+```
 
 ## Updating
 
@@ -141,94 +142,24 @@ Claude Code third-party marketplaces don't auto-update by default:
 /reload-plugins
 ```
 
-No re-add or reinstall needed. Copilot users re-run `install-skills.sh`.
-
----
-
-## Maintainers
-
-The source of truth is the `datasqrl-plugin/` directory of
-**[DataSQRL/code-agent](https://github.com/DataSQRL/code-agent)**. This repo is **generated** from
-it by CI on every merge to `main` — never hand-edit it; open PRs against `code-agent`.
-
-### Layout
-
-The repository root is simultaneously the marketplace root, the plugin root, and the skills tree:
-
-```
-.claude-plugin/{marketplace.json, plugin.json}
-.codex-plugin/plugin.json
-.cursor-plugin/plugin.json
-skills/<name>/SKILL.md          ← one shared tree, all three manifests point at it
-scripts/datasqrl-agent.sh            ← byte-identical copy of agent/datasqrl-agent.sh (CI-enforced)
-scripts/datasqrl-cloud.sh       ← DataSQRL Cloud API client; lives only here
-install-skills.sh               ← Copilot only
-```
-
-Flat on purpose: each agent looks for *its own* manifest at the root of whatever repo it is given,
-so one published repo installs in all three. The Claude marketplace entry uses `"source": "./"`.
-
-**Do not add a `skills` key to `.claude-plugin/plugin.json`.** With a marketplace-root source, a
-declared `skills` list becomes the *complete* set and the default `skills/` scan stops running —
-so adding one directory would silently hide all the others. Leaving the key out keeps the full
-scan. (That same rule is what would let a second plugin entry carve out its own subset later.)
-
-### Local development
-
-In the source repo, **`agent/datasqrl-agent.sh` is canonical** and `scripts/datasqrl-agent.sh` is a
-byte-identical copy. After editing the launcher:
-
-```bash
-./agent/sync-launcher.sh          # refresh the copy
-./agent/sync-launcher.sh --check  # what CI runs; non-zero if they differ
-```
-
-CI fails the build when they diverge, so the copy cannot drift silently.
+No re-add or reinstall needed. Copilot users pull this repository, re-run `install-skills.sh`,
+and download the launcher again. [Releases](https://github.com/DataSQRL/datasqrl-plugin/releases)
+lists what changed in each version.
 
-**Why a copy and not a symlink.** All three plugin hosts **copy** a plugin into a local cache on
-install, and a relative symlink pointing *outside* the plugin directory does not survive that copy —
-the installed plugin gets an empty `scripts/` and every skill fails to find the launcher. This
-repository shipped a symlink until it was caught, and local installs were silently broken by it.
-Do not reintroduce one.
+## Data handling and telemetry
 
-To trial local changes, from your `code-agent` working tree:
+The plugin has no telemetry of its own, and the agent's telemetry is off by default. A run sends
+your prompts and project code to the model provider you choose; `deploy` and `promote` talk to
+DataSQRL Cloud.
+[DATA_HANDLING.md](DATA_HANDLING.md) lists what runs where, which credentials are read, and what
+leaves your machine.
 
-```
-/plugin marketplace add /absolute/path/to/code-agent/datasqrl-plugin
-/plugin install datasqrl@datasqrl
-```
+## Contributing
 
-After editing a manifest, refresh Claude Code's cached copy:
+Issues and pull requests are welcome. [CONTRIBUTING.md](CONTRIBUTING.md) covers how to test a
+change locally and the checks CI runs.
+Everyone taking part follows the [Code of Conduct](CODE_OF_CONDUCT.md).
 
-```
-/plugin marketplace update datasqrl
-/reload-plugins
-```
+## License
 
-Edits to a `SKILL.md` take effect immediately — no reload needed.
-
-**Two things that have bitten this plugin before:**
-
-1. **After a stale install, `scripts/` can be empty.** Any plugin cached before the launcher became
-   a real file has an empty `scripts/` directory, and every skill fails to find `datasqrl-agent.sh`.
-   Check the installed copy rather than the source tree:
-   ```bash
-   ls -l ~/.claude/plugins/cache/datasqrl/datasqrl/*/scripts/
-   ```
-   If it is empty, reinstall: `/plugin marketplace update datasqrl` then `/reload-plugins`. Old
-   caches under a previous plugin name (e.g. `datasqrl-code-agent/0.1.0/`) are worth deleting —
-   they hold a launcher predating `--detach`, and a search-based fallback could otherwise find one.
-2. **`${CLAUDE_PLUGIN_ROOT}` is a text substitution, not a shell variable.** Claude Code replaces
-   the literal `${CLAUDE_PLUGIN_ROOT}` in *skill content* with the plugin's absolute path before the
-   model reads it. It is exported as a real environment variable only to hook processes and MCP/LSP
-   subprocesses.
-
-   So the skills must use the bare placeholder. Any shell-flavoured variant — `${CLAUDE_PLUGIN_ROOT:+…}`,
-   `$CLAUDE_PLUGIN_ROOT` without braces, a default like `${CLAUDE_PLUGIN_ROOT:-…}` — does **not**
-   match what Claude Code substitutes, reaches the model unchanged, and then expands to nothing in
-   the shell. The symptom is a path starting at `/scripts/...` or a bare `datasqrl-agent.sh`, and the
-   agent hard-coding an absolute path to recover.
-
-   The second line (`[ -f "$CODEAGENT" ] || CODEAGENT=datasqrl-agent.sh`) is what makes the same snippet
-   work in Codex/Cursor/Copilot, where the placeholder is never substituted and the launcher comes
-   from `PATH`.
+Licensed under the [Apache License, Version 2.0](LICENSE).
diff --git a/install-skills.sh b/install-skills.sh
index e509a1c..f96521d 100755
--- a/install-skills.sh
+++ b/install-skills.sh
@@ -1,4 +1,5 @@
 #!/bin/bash
+# SPDX-License-Identifier: Apache-2.0
 # Install the DataSQRL skills into a repository for coding agents that have no plugin system.
 #
 # Claude Code, Codex and Cursor all install this directory as a PLUGIN and do not need this
@@ -51,7 +52,7 @@ else
 NOTE: datasqrl-agent.sh is not on your PATH, and the skills invoke it by that name.
 Install it with:
 
-  curl -fsSL https://raw.githubusercontent.com/DataSQRL/datasqrl-plugin/main/scripts/datasqrl-agent.sh \\
+  curl -fsSL https://github.com/DataSQRL/datasqrl-plugin/releases/latest/download/datasqrl-agent.sh \\
     -o /usr/local/bin/datasqrl-agent.sh && chmod +x /usr/local/bin/datasqrl-agent.sh
 EOF
 fi
diff --git a/scripts/datasqrl-agent.sh b/scripts/datasqrl-agent.sh
index 8764787..cc86e27 100755
--- a/scripts/datasqrl-agent.sh
+++ b/scripts/datasqrl-agent.sh
@@ -1,18 +1,5 @@
 #!/bin/bash
-#
-# TWO BYTE-IDENTICAL COPIES OF THIS FILE EXIST. Edit only the first:
-#
-#   agent/datasqrl-agent.sh                     <- canonical; edit this one
-#   datasqrl-plugin/scripts/datasqrl-agent.sh   <- copy shipped inside the plugin
-#
-# then run:  ./agent/sync-launcher.sh
-#
-# CI fails if they differ, so the copy cannot drift silently. A symlink would be
-# the obvious way to avoid the duplication, and it does not work: Claude Code,
-# Codex and Cursor all COPY a plugin into a local cache on install, and a
-# relative symlink whose target lives outside the plugin directory is dropped by
-# that copy — the installed plugin ends up with an empty scripts/ and every skill
-# fails to find this launcher.
+# SPDX-License-Identifier: Apache-2.0
 #
 # Run DataSQRL Code Agent with local or cloud MCP server.
 # Run this script from the workspace directory containing your DataSQRL project.
@@ -1091,12 +1078,22 @@ GATE_WS="$CONTAINER_WORKSPACE"
 # Capture host identifiers for log correlation across planning/implementation runs
 HOST_WORKSPACE_FOLDER=$(basename "$HOST_WS")
 if [[ "$OSTYPE" == "darwin"* ]]; then
-    HOST_MAC_ID=$(ifconfig en0 2>/dev/null | awk '/ether/{print $2; exit}')
-    [ -z "$HOST_MAC_ID" ] && HOST_MAC_ID=$(ifconfig 2>/dev/null | awk '/ether/{print $2; exit}')
+    _mac=$(ifconfig en0 2>/dev/null | awk '/ether/{print $2; exit}')
+    [ -z "$_mac" ] && _mac=$(ifconfig 2>/dev/null | awk '/ether/{print $2; exit}')
 else
-    HOST_MAC_ID=$(ip link show 2>/dev/null | awk '/link\/ether/{print $2; exit}')
-    [ -z "$HOST_MAC_ID" ] && HOST_MAC_ID=$(cat /sys/class/net/"$(ls /sys/class/net/ 2>/dev/null | grep -v lo | head -1)"/address 2>/dev/null)
+    _mac=$(ip link show 2>/dev/null | awk '/link\/ether/{print $2; exit}')
+    if [ -z "$_mac" ]; then
+        # The first interface with a real address; /sys/class/net also holds files such as
+        # bonding_masters and tunnels whose address is all zeros.
+        for _if in /sys/class/net/*; do
+            [ "${_if##*/}" = lo ] && continue
+            _mac=$(cat "$_if/address" 2>/dev/null)
+            case "$_mac" in ""|00:00:00:00:00:00) _mac="" ;; *) break ;; esac
+        done
+    fi
 fi
+HOST_MAC_ID="$_mac"
+unset _mac _if
 
 # Build docker arguments.
 # --name is the per-project lock (see "Run identity" above) and is applied in BOTH modes on
diff --git a/scripts/datasqrl-cloud.sh b/scripts/datasqrl-cloud.sh
index ad42d1d..c2624a0 100755
--- a/scripts/datasqrl-cloud.sh
+++ b/scripts/datasqrl-cloud.sh
@@ -1,4 +1,5 @@
 #!/bin/bash
+# SPDX-License-Identifier: Apache-2.0
 #
 # DataSQRL Cloud API client for the `deploy` skill.
 #

From 87895833b9694f2e9eb8a1009b8d2e16fcf36f08 Mon Sep 17 00:00:00 2001
From: Hasan Alp Caferoglu <alp.caferoglu@gmail.com>
Date: Fri, 9 Oct 2026 23:43:33 +0300
Subject: [PATCH 2/3] ci: name the check job build to satisfy the DataSQRL
 organization ruleset

---
 .github/workflows/ci.yml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 0780ae1..0c60ced 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -9,8 +9,9 @@ permissions:
   contents: read
 
 jobs:
-  check:
-    name: Check plugin
+  # The DataSQRL organization ruleset requires a status check named "build" on main.
+  build:
+    name: build
     runs-on: ubuntu-latest
     timeout-minutes: 10
     steps:

From 93aa240eb7ed6983b03d2d8ba405a2b2c26f9fa3 Mon Sep 17 00:00:00 2001
From: Hasan Alp Caferoglu <alp.caferoglu@gmail.com>
Date: Sat, 10 Oct 2026 00:27:02 +0300
Subject: [PATCH 3/3] docs: add a pull request template

---
 .github/pull_request_template.md | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 .github/pull_request_template.md

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000..49ba3b6
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,24 @@
+## What does this change?
+
+<!-- One or two sentences. Link the issue it fixes, e.g. "Fixes #12". -->
+
+## Area
+
+- [ ] Skills
+- [ ] Launcher (`scripts/datasqrl-agent.sh`)
+- [ ] Cloud client (`scripts/datasqrl-cloud.sh`)
+- [ ] Manifests
+- [ ] CI
+- [ ] Docs
+
+## How did you test it?
+
+<!-- For example: installed from your clone in Claude Code and ran the plan skill on a sample project. -->
+
+## Checklist
+
+- [ ] The PR title starts with a type such as `feat:`, `fix:` or `docs:`
+- [ ] `.github/check-plugin.sh` passes
+- [ ] Skills contain no SQRL and no HTML comments
+- [ ] A launcher change that needs a new agent image option waits until that image is published
+- [ ] README or DATA_HANDLING.md is updated if behavior or data handling changed