detectkit 0.13.1__tar.gz → 0.15.0__tar.gz

{detectkit-0.13.1/detectkit.egg-info → detectkit-0.15.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: detectkit
-Version: 0.13.1
+Version: 0.15.0
 Summary: Metric monitoring with automatic anomaly detection
 Author: detectkit team
 License: MIT
@@ -87,7 +87,7 @@ Dynamic: license-file
 - **Database agnostic** — ClickHouse, PostgreSQL, MySQL
 - **Idempotent** — resume from interruptions, no duplicate processing
 - **CLI** — `dtk init`, `dtk run --select`, `dtk unlock`, `dtk clean`, tag-based selectors
-- **AI-native onboarding** — `dtk init-claude` sets up Claude Code context (CLAUDE.md + rules + a metric-scaffolding skill) so an assistant can help you build metrics out of the box
+- **AI-native onboarding** — `dtk init-claude` sets up Claude Code context (CLAUDE.md + rules + three skills) so an assistant can scaffold metrics, configure databases, and file feedback upstream
 
 ## Installation
 

{detectkit-0.13.1 → detectkit-0.15.0}/README.md

@@ -19,7 +19,7 @@
 - **Database agnostic** — ClickHouse, PostgreSQL, MySQL
 - **Idempotent** — resume from interruptions, no duplicate processing
 - **CLI** — `dtk init`, `dtk run --select`, `dtk unlock`, `dtk clean`, tag-based selectors
-- **AI-native onboarding** — `dtk init-claude` sets up Claude Code context (CLAUDE.md + rules + a metric-scaffolding skill) so an assistant can help you build metrics out of the box
+- **AI-native onboarding** — `dtk init-claude` sets up Claude Code context (CLAUDE.md + rules + three skills) so an assistant can scaffold metrics, configure databases, and file feedback upstream
 
 ## Installation
 

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit/__init__.py

@@ -4,7 +4,7 @@ detectk - Anomaly Detection for Time-Series Metrics
 A Python library for data analysts and engineers to monitor metrics with automatic anomaly detection.
 """
 
-__version__ = "0.13.1"
+__version__ = "0.15.0"
 
 from detectkit.core.interval import Interval
 from detectkit.core.models import ColumnDefinition, TableModel

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit/alerting/channels/base.py

@@ -32,10 +32,14 @@ class AlertData:
         consecutive_count: Number of consecutive anomalies
         is_recovery: True for recovery notifications
         is_no_data: True for missing-data alerts (no_data_alert)
-        project_name: Optional ``detectkit_project.yml`` name. Surfaces
-            as ``{project_name}`` in templates and as a ``[name] `` prefix
-            in the default error title. Lets multiple projects share the
-            same alert channel without ambiguity.
+        project_name: Optional ``detectkit_project.yml`` name. Surfaces as
+            ``{project_name}`` / ``{project_name_prefix}`` in templates and, by
+            default, as a ``[name] `` prefix on every alert title/headline
+            (anomaly, recovery, no-data, error) plus a brand-paired footer
+            ("detectkit · name" on webhook/email). The detectkit pipeline stamps
+            it from the project config; direct-API callers leave it ``None`` and
+            render unchanged. Lets multiple projects share one alert channel —
+            keeping the default brand bot name + avatar — without ambiguity.
 
     Alert-rule fields (``min_detectors``, ``direction_policy``,
     ``consecutive_required``, ``detector_count``) describe *why the alert
@@ -450,7 +454,7 @@ class BaseAlertChannel(ABC):
             Default template string
         """
         return (
-            "🔴 Alert: {metric_name}\n"
+            "🔴 {project_name_prefix}Alert: {metric_name}\n"
             "{description_line}"
             "Quorum {detector_count}/{min_detectors} · "
             "direction {direction} (policy {direction_policy}) · "
@@ -476,7 +480,7 @@ class BaseAlertChannel(ABC):
             Default recovery template string
         """
         return (
-            "🟢 Alert cleared: {metric_name}\n"
+            "🟢 {project_name_prefix}Alert cleared: {metric_name}\n"
             "{description_line}"
             "The alert condition no longer holds — "
             "the metric is back within expected bounds.\n"
@@ -500,7 +504,7 @@ class BaseAlertChannel(ABC):
         Returns:
             Default title template string
         """
-        return "🔴 Alert: {metric_name}"
+        return "🔴 {project_name_prefix}Alert: {metric_name}"
 
     def get_default_recovery_title_template(self) -> str:
         """
@@ -509,7 +513,7 @@ class BaseAlertChannel(ABC):
         Returns:
             Default recovery title template string
         """
-        return "🟢 Alert cleared: {metric_name}"
+        return "🟢 {project_name_prefix}Alert cleared: {metric_name}"
 
     def get_default_no_data_template(self) -> str:
         """
@@ -519,7 +523,7 @@ class BaseAlertChannel(ABC):
         has no datapoint (no row OR row with NULL/NaN value).
         """
         return (
-            "🟡 No data for metric: {metric_name}\n"
+            "🟡 {project_name_prefix}No data for metric: {metric_name}\n"
             "{description_line}"
             "Time: {timestamp}\n"
             "Status: query returned no datapoint for the latest interval\n"
@@ -529,12 +533,12 @@ class BaseAlertChannel(ABC):
 
     def get_default_no_data_title_template(self) -> str:
         """Get default title template for no-data alerts."""
-        return "🟡 No data: {metric_name}"
+        return "🟡 {project_name_prefix}No data: {metric_name}"
 
     def get_default_error_template(self) -> str:
         """Default body template for project-level error alerts."""
         return (
-            "🔵 Pipeline failed for metric: {metric_name}\n"
+            "🔵 {project_name_prefix}Pipeline failed for metric: {metric_name}\n"
             "{description_line}"
             "Time: {timestamp}\n"
             "Error: {error_type}: {error_message}\n"

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit/alerting/channels/email.py

@@ -74,7 +74,7 @@ class EmailChannel(BaseAlertChannel):
         smtp_username: str | None = None,
         smtp_password: str | None = None,
         use_tls: bool = True,
-        subject_template: str = "🔴 Alert: {metric_name}",
+        subject_template: str = "🔴 {project_name_prefix}Alert: {metric_name}",
         from_name: str = BRAND_USERNAME,
         template: str | None = None,
         **kwargs,
@@ -144,10 +144,18 @@ class EmailChannel(BaseAlertChannel):
         # of a bot display name. formataddr quotes the name when required.
         msg["From"] = formataddr((self.from_name, self.from_email))
         msg["To"] = ", ".join(self.to_emails)
-        # Strip CR/LF from the metric name before it reaches the Subject header
-        # so a metric name can never inject extra email headers.
+        # Strip CR/LF from the metric *and* project name before they reach the
+        # Subject header so neither can inject extra email headers. The project
+        # prefix ("[my_project] ") makes the inbox row distinguishable when
+        # several projects email the same address.
         subject_metric = alert_data.metric_name.replace("\r", " ").replace("\n", " ")
-        msg["Subject"] = self.subject_template.format(metric_name=subject_metric)
+        project_clean = (alert_data.project_name or "").replace("\r", " ").replace("\n", " ")
+        project_prefix = f"[{project_clean}] " if project_clean else ""
+        msg["Subject"] = self.subject_template.format(
+            metric_name=subject_metric,
+            project_name_prefix=project_prefix,
+            project_name=project_clean,
+        )
 
         # Attach both parts. In multipart/alternative the LAST part is the
         # preferred one, so HTML (the branded card) is shown when supported and
@@ -247,6 +255,8 @@ class EmailChannel(BaseAlertChannel):
             f'font-size:4px;background-color:{accent};">&nbsp;</td></tr>'
             # header: logo + wordmark + status pill
             f"{self._header_html(accent, pill)}"
+            # project eyebrow (small label above the metric, only when set)
+            f"{self._eyebrow_html(ctx['project_name'])}"
             # title
             f'<tr><td style="padding:6px 24px 2px 24px;font-family:{_SANS};font-size:22px;'
             f'font-weight:bold;color:{_INK};mso-line-height-rule:exactly;line-height:28px;">'
@@ -258,6 +268,17 @@ class EmailChannel(BaseAlertChannel):
             "</table></td></tr></table></body></html>"
         )
 
+    def _eyebrow_html(self, project_name: str) -> str:
+        """Small uppercase project label above the metric title (empty if unset)."""
+        if not project_name:
+            return ""
+        return (
+            f'<tr><td style="padding:10px 24px 0 24px;font-family:{_SANS};font-size:11px;'
+            f"font-weight:bold;letter-spacing:0.5px;color:{_FAINT};text-transform:uppercase;"
+            f'mso-line-height-rule:exactly;line-height:14px;">'
+            f"{html.escape(project_name)}</td></tr>"
+        )
+
     def _header_html(self, accent: str, pill: str) -> str:
         """Logo + wordmark (real text) + colored status pill row."""
         return (
@@ -432,11 +453,16 @@ class EmailChannel(BaseAlertChannel):
     def _footer_html(self, alert_data: AlertData) -> str:
         cc = self.format_mentions(alert_data.mentions)
         cc_html = f" &middot; {html.escape(cc)}" if cc else ""
+        # Pair the brand with the project name ("Sent by detectkit · my_project")
+        # so the source project is clear even past the subject/eyebrow.
+        project_html = (
+            f" &middot; {html.escape(alert_data.project_name)}" if alert_data.project_name else ""
+        )
         return (
             f'<tr><td bgcolor="{_SURFACE}" style="background-color:{_SURFACE};'
             f"border-top:1px solid {_BORDER};padding:14px 24px;font-family:{_SANS};"
             f'font-size:12px;color:{_FAINT};mso-line-height-rule:exactly;line-height:16px;">'
-            f"Sent by detectkit{cc_html}</td></tr>"
+            f"Sent by detectkit{project_html}{cc_html}</td></tr>"
         )
 
     def format_mentions(self, mentions: list[str]) -> str:

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit/alerting/channels/telegram.py

@@ -148,7 +148,12 @@ class TelegramChannel(BaseAlertChannel):
             return html.escape(str(value))
 
         metric = esc(ctx["metric_name"])
-        lines: list[str] = [f"{dot} <b>{word} · {metric}</b>"]
+        # Lead the headline with the project name (when set) so multiple
+        # projects sharing one chat stay distinguishable — Telegram has no
+        # footer/avatar override, so this prefix is the only project cue.
+        proj = ctx["project_name"]
+        head_prefix = f"[{esc(proj)}] " if proj else ""
+        lines: list[str] = [f"{dot} <b>{head_prefix}{word} · {metric}</b>"]
 
         if ctx["description"]:
             lines.append(f"<i>{esc(self._cap(ctx['description'], _DESC_CAP))}</i>")

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit/alerting/channels/webhook.py

@@ -189,8 +189,13 @@ class WebhookChannel(BaseAlertChannel):
             attachment["title_link"] = alert_data.dashboard_url
 
         # Brand the attachment footer (reliable on Slack even when top-level
-        # username/icon are locked to the app install).
-        attachment["footer"] = self.username or BRAND_USERNAME
+        # username/icon are locked to the app install). Pair the brand name with
+        # the project name when set ("detectkit · my_project") so two projects
+        # posting to the same channel stay distinguishable even past the title.
+        footer = self.username or BRAND_USERNAME
+        if alert_data.project_name:
+            footer = f"{footer} · {alert_data.project_name}"
+        attachment["footer"] = footer
         if self.icon_url:
             attachment["footer_icon"] = self.icon_url
         # Slack-only sugar: a real timestamp under the footer. Mattermost

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit/alerting/orchestrator/_base.py

@@ -25,6 +25,7 @@ class _OrchestratorBase:
         mentions: list[str] | None = None,
         dashboard_url: str | None = None,
         links: dict[str, str] | None = None,
+        project_name: str | None = None,
     ):
         self.metric_name = metric_name
         self.interval = interval
@@ -37,6 +38,11 @@ class _OrchestratorBase:
         self.mentions = mentions or []
         self.dashboard_url = dashboard_url
         self.links = links or {}
+        # Optional project name (``detectkit_project.yml`` ``name``). Stamped
+        # onto every AlertData so channels can label which project an alert
+        # came from — keeps multiple projects sharing one channel distinct
+        # while the bot keeps the default brand name + avatar.
+        self.project_name = project_name
 
     @staticmethod
     def _group_by_timestamp(

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit/alerting/orchestrator/_decision.py

@@ -241,6 +241,7 @@ class _DecisionMixin(_OrchestratorBase):
             mentions=self.mentions,
             dashboard_url=self.dashboard_url,
             links=self.links,
+            project_name=self.project_name,
             # Alert rule the message foregrounds: configured thresholds plus
             # the observed quorum size that satisfied them.
             min_detectors=self.conditions.min_detectors,
@@ -300,6 +301,7 @@ class _DecisionMixin(_OrchestratorBase):
             mentions=self.mentions,
             dashboard_url=self.dashboard_url,
             links=self.links,
+            project_name=self.project_name,
         )
 
     def get_last_complete_point(self, now: datetime | None = None) -> datetime:

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit/alerting/orchestrator/_recovery.py

@@ -178,6 +178,7 @@ class _RecoveryMixin(_OrchestratorBase):
             mentions=self.mentions,
             dashboard_url=self.dashboard_url,
             links=self.links,
+            project_name=self.project_name,
             # Echo the rule that had fired so the recovery message names the
             # same alert condition that just cleared.
             min_detectors=self.conditions.min_detectors,

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit/cli/assets/claude/CLAUDE.section.md

@@ -26,7 +26,7 @@ version — **read the relevant one on demand** instead of guessing:
 | Choosing/tuning detectors, preprocessing, trends, seasonality | `.claude/rules/detectkit/detectors.md` |
 | Alert rules (quorum/direction/consecutive), cooldown, recovery, templates | `.claude/rules/detectkit/alerting.md` |
 
-### Set up & scaffold (skills)
+### Skills
 
 - **First-time setup** — use the **`dtk-setup-project`** skill to configure the
   database connection in `profiles.yml` (the `dtk init` placeholder ships example
@@ -34,6 +34,11 @@ version — **read the relevant one on demand** instead of guessing:
   channel.
 - **A new metric** — use the **`dtk-new-metric`** skill; it walks the config out
   to a YAML file that validates and is ready to run.
+- **Hit a detectkit bug, or have feedback** — once you've ruled out a local
+  config fix (see the gotchas below), use the **`dtk-feedback`** skill to file a
+  redacted bug report, feature request, or comment as a GitHub issue on the
+  upstream repo. It auto-collects the diagnostic context, strips every secret,
+  and never submits without showing you the exact text first.
 
 ### Gotchas that bite (keep these in mind)
 

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit/cli/assets/claude/rules/alerting.md

@@ -158,7 +158,9 @@ With no custom `template`, each channel renders a structured, branded message
 shared value computation lives in one place (`BaseAlertChannel.build_context`),
 so templates and native rendering stay consistent. Every alert title/headline
 leads with a colored **status circle** — 🔴 anomaly, 🟢 recovery, 🟡 no-data,
-🔵 pipeline error — so the status reads from color alone.
+🔵 pipeline error — so the status reads from color alone. It also leads with the
+**project name** as a `[name] ` prefix (from `detectkit_project.yml`) — see
+[Project label](#project-label-multi-project-channels) below.
 
 - **Slack / Mattermost / generic webhook** — one message *attachment* with a
   status-colored accent bar, a clickable title (the metric; links to
@@ -181,6 +183,25 @@ leads with a colored **status circle** — 🔴 anomaly, 🟢 recovery, 🟡 no-
   table, a monospace params box, an optional "Open dashboard" button, and a
   footer. The plain-text body remains the multipart fallback.
 
+## Project label (multi-project channels)
+
+The bot keeps the **detectkit brand** name + avatar by default (so users rarely
+override them). To still tell apart two projects posting to the **same** channel,
+detectkit stamps the project name (`detectkit_project.yml` → `name`) onto every
+alert and shows it by default — no config needed:
+
+- **Title / headline / subject** lead with a `[name] ` prefix on every kind
+  (anomaly, recovery, no-data, error): `🔴 [payments] Alert: api_error_rate`.
+- **Webhook (Slack/Mattermost)** also pairs it in the footer: `detectkit · payments`.
+- **Telegram** carries it in the bold headline (no footer/avatar to override).
+- **Email** prefixes the subject, shows a small project eyebrow above the metric,
+  and pairs it in the footer (`Sent by detectkit · payments`).
+
+It is exposed to custom templates as `{project_name}` and `{project_name_prefix}`
+(`"[name] "` when set, else `""`). Direct library/API callers that don't set it
+render unchanged. The `name` is informational only (it does not key any `_dtk_*`
+table), so renaming it is safe — spaces are allowed for a prettier label.
+
 ## Multiple alert configs per metric
 
 `alerting:` may be a **list** of independent blocks, each with its own channels,
@@ -210,6 +231,7 @@ referenced by path). Key variables:
 | Variable | Meaning |
 |---|---|
 | `{metric_name}`, `{description}` / `{description_line}` | identity |
+| `{project_name}` / `{project_name_prefix}` | project label (`"[name] "` prefix, or `""`) |
 | `{timestamp}`, `{timezone}` | when (display tz via `alerting.timezone`, default UTC) |
 | `{value}` / `{value_display}` | metric value (`value_display` is NaN-safe) |
 | `{confidence_lower}` / `{confidence_upper}` / `{confidence_interval}` | bounds |

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit/cli/assets/claude/rules/project.md

@@ -9,7 +9,9 @@ errors (not empty strings).
 ## `detectkit_project.yml`
 
 ```yaml
-name: my_monitoring            # required — project identifier (logs, error-alert titles)
+name: my_monitoring            # required — project identifier; also labels every
+                               # alert ("[my_monitoring] Alert: …") so multiple
+                               # projects on one channel stay distinct (alerting.md)
 version: "1.0"                 # optional (default "1.0")
 default_profile: prod          # profile name from profiles.yml
 
@@ -57,8 +59,10 @@ error_alerting:
   via cron cadence). Channel send failures are swallowed so a flaky webhook
   can't crash the run.
 - Extra template variables: `{error_type}`, `{error_message}`, `{status}`
-  (always `"ERROR"`), `{project_name}`, `{project_name_prefix}` (=
-  `"[<name>] "` when `name` set — keeps multi-project channels distinguishable).
+  (always `"ERROR"`). `{project_name}` / `{project_name_prefix}` (=
+  `"[<name>] "` when `name` set) are available here **and in every other alert
+  template** — and by default lead the title/headline on all channels, keeping
+  multi-project channels distinguishable (see `alerting.md` → Project label).
 
 ## `profiles.yml`
 

detectkit-0.15.0/detectkit/cli/assets/claude/skills/dtk-feedback/SKILL.md

@@ -0,0 +1,155 @@
+---
+name: dtk-feedback
+description: >-
+  Report a detectkit bug, request a feature, or send feedback to the maintainers
+  as a GitHub issue on the upstream repo (alexeiveselov92/detectkit). Use when a
+  dtk command errors or behaves unexpectedly and it looks like a detectkit defect
+  (not the user's config), when the user wishes detectkit did something it
+  doesn't, or when they ask to report/file an issue, send feedback, or contact
+  the maintainers. Auto-collects diagnostic context, redacts all secrets, and
+  never submits without explicit confirmation.
+---
+
+# Send feedback to the detectkit maintainers
+
+Turn a problem, a wish, or a comment into a clear GitHub issue on the upstream
+repo **`alexeiveselov92/detectkit`** — carrying the diagnostic context
+maintainers need and **leaking no secrets**. You are filing a *public* issue on
+the user's behalf: never submit anything without showing the exact text and
+getting an explicit "yes".
+
+This skill is the procedure; the reference for ruling out config problems lives
+under `.claude/rules/detectkit/`.
+
+## Step 0 — Decide whether this belongs upstream
+
+- **Bug** — a `dtk` command errors or produces clearly wrong output, **and**
+  you've ruled out a local config/usage mistake (Step 1).
+- **Feature request** — the user needs detectkit to do something it doesn't.
+- **Feedback / question** — a comment, confusion, or rough edge worth surfacing.
+
+Do **not** open an issue for the user's own SQL, data, database, or
+configuration mistakes — those are fixed locally with the rules files, not
+reported as detectkit bugs. Only genuine detectkit behavior goes upstream.
+
+## Step 1 — Rule out config first (for "it doesn't work")
+
+Before calling something a bug, confirm it isn't a configuration or usage
+problem. Read the matching `.claude/rules/detectkit/` file and check the usual
+gotchas:
+
+- the loading query filters on `{{ dtk_start_time }}` **and** `{{ dtk_end_time }}`;
+- metric `name` is unique across the project;
+- `profiles.yml` has the right location fields (`internal_database`/`data_database`,
+  or Postgres schemas) and a `default_profile` that exists;
+- `alert_cooldown` is set; channels referenced by metrics exist.
+
+If a local fix exists, **do that and stop** — don't file an issue. Escalate only
+what is genuinely a detectkit defect.
+
+## Step 2 — Gather context (do this for the user, don't make them dig)
+
+Collect automatically:
+
+- `dtk --version` — the detectkit version (**always** include it).
+- Python version (`python3 --version`) and OS.
+- The database backend **type only** (`clickhouse` / `postgres` / `mysql`) from
+  `profiles.yml`'s `type:` — never the host, port, or credentials.
+
+For a **bug**, also gather:
+
+- the exact command that was run;
+- the full error message / traceback;
+- what the user expected vs. what happened;
+- a **minimal reproduction** — the failing metric YAML and/or SQL, with every
+  secret stripped (Step 3).
+
+## Step 3 — Redact secrets (mandatory — before anything is shown or sent)
+
+This is a public issue. Strip from every snippet you include:
+
+- passwords, tokens, `bot_token`, `smtp_password`, API keys;
+- `webhook_url`s, `chat_id`s, email addresses;
+- hostnames, IPs, ports, and real database / schema / table names;
+- the resolved value of anything inside `{{ env_var('…') }}` or `${…}` — keep the
+  `env_var(...)` shape, drop the value.
+
+Replace with placeholders like `<redacted>`, `<your-host>`, `<your_table>` while
+keeping the structure intact so the bug is still reproducible. **If you're not
+sure whether something is sensitive, redact it.**
+
+## Step 4 — Search for duplicates
+
+```bash
+gh issue list --repo alexeiveselov92/detectkit --search "<keywords>" --state all
+```
+
+If a matching issue already exists, offer to **add a comment** or a 👍 reaction
+instead of opening a new one:
+
+```bash
+gh issue comment <number> --repo alexeiveselov92/detectkit --body "<note>"
+```
+
+This gives maintainers signal on frequency instead of a pile of duplicates.
+
+## Step 5 — Draft the issue
+
+Write a specific title (the actual symptom in a few words, not "bug"). Pick the
+body template by type:
+
+- **Bug** — `Summary` / `Environment` (detectkit version, Python, OS, backend) /
+  `Steps to reproduce` / `Expected` / `Actual` (with the traceback in a fenced
+  code block) / `Minimal config` (redacted).
+- **Feature request** — `Problem` (the underlying need, not just the proposed
+  fix) / `Proposed behavior` / `Alternatives considered`.
+- **Feedback** — free-form, concrete and respectful.
+
+End the body with an attribution marker so maintainers can see it came through
+the assistant funnel and on which version:
+
+```
+_Filed via the dtk init-claude assistant (detectkit <version>)._
+```
+
+## Step 6 — Preview and confirm (no silent submits)
+
+Show the user the **full** title and body exactly as they will be posted, and
+the target repo. Ask them to confirm: secrets redacted? right repo? Proceed to
+Step 7 only on an explicit "yes". If they want edits, revise and re-preview.
+
+## Step 7 — Submit
+
+**Preferred — `gh` CLI** (check it's installed and authenticated first with
+`gh auth status`). Write the body to a temp file to avoid shell-escaping the
+markdown/traceback:
+
+```bash
+gh issue create --repo alexeiveselov92/detectkit \
+  --title "<title>" --body-file <tmpfile>
+```
+
+Tag the issue so maintainers can triage assistant-filed reports: add the type
+label (`--label bug` / `--label enhancement`) **and** `--label "via:assistant"`.
+Labels must already exist on the repo, so if `gh` reports an unknown label,
+**retry without the failing label(s)** — never fail the report over a missing
+label. (Attribution also lives in the Step 5 body marker, so maintainers can
+filter with `in:body "Filed via the dtk init-claude assistant"` even before the
+`via:assistant` label exists.) Return the issue URL to the user.
+
+**Fallback — no `gh`, or not authenticated.** Build a prefilled "new issue" URL
+and hand it to the user to open and submit in their browser:
+
+```
+https://github.com/alexeiveselov92/detectkit/issues/new?title=<url-encoded>&body=<url-encoded>
+```
+
+URL-encode both fields. If the body is too long for a URL, give the user the
+title plus the body text to paste, and the plain link
+`https://github.com/alexeiveselov92/detectkit/issues/new`.
+
+## Step 8 — Close the loop
+
+Give the user the issue URL (or the prefilled link), mention they can subscribe
+for updates, and — if you also worked around the bug locally — restate that
+local fix so they're unblocked right now, not just waiting on the issue.

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit/cli/commands/init_claude.py

@@ -11,7 +11,8 @@ It writes three things into the target directory:
   injected/refreshed between HTML-comment markers (existing content is kept).
 - ``.claude/rules/detectkit/`` — the reference docs the assistant reads on
   demand (overview, cli, project, metrics, detectors, alerting).
-- ``.claude/skills/`` — user-facing skills (``dtk-new-metric``).
+- ``.claude/skills/`` — user-facing skills (``dtk-setup-project``,
+  ``dtk-new-metric``, ``dtk-feedback``).
 
 The source of truth for all of the above lives in ``detectkit/cli/assets/claude``
 and ships with the package, so re-running this command after upgrading detectkit

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit/orchestration/task_manager/_alert_step.py

@@ -64,6 +64,7 @@ class _AlertStepMixin(_TaskManagerBase):
                 mentions=alerting_config.mentions,
                 dashboard_url=alerting_config.dashboard_url,
                 links=alerting_config.links,
+                project_name=getattr(self.project_config, "name", None),
             )
 
             last_point = orchestrator.get_last_complete_point()

{detectkit-0.13.1 → detectkit-0.15.0/detectkit.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: detectkit
-Version: 0.13.1
+Version: 0.15.0
 Summary: Metric monitoring with automatic anomaly detection
 Author: detectkit team
 License: MIT
@@ -87,7 +87,7 @@ Dynamic: license-file
 - **Database agnostic** — ClickHouse, PostgreSQL, MySQL
 - **Idempotent** — resume from interruptions, no duplicate processing
 - **CLI** — `dtk init`, `dtk run --select`, `dtk unlock`, `dtk clean`, tag-based selectors
-- **AI-native onboarding** — `dtk init-claude` sets up Claude Code context (CLAUDE.md + rules + a metric-scaffolding skill) so an assistant can help you build metrics out of the box
+- **AI-native onboarding** — `dtk init-claude` sets up Claude Code context (CLAUDE.md + rules + three skills) so an assistant can scaffold metrics, configure databases, and file feedback upstream
 
 ## Installation
 

{detectkit-0.13.1 → detectkit-0.15.0}/detectkit.egg-info/SOURCES.txt

@@ -39,6 +39,7 @@ detectkit/cli/assets/claude/rules/detectors.md
 detectkit/cli/assets/claude/rules/metrics.md
 detectkit/cli/assets/claude/rules/overview.md
 detectkit/cli/assets/claude/rules/project.md
+detectkit/cli/assets/claude/skills/dtk-feedback/SKILL.md
 detectkit/cli/assets/claude/skills/dtk-new-metric/SKILL.md
 detectkit/cli/assets/claude/skills/dtk-setup-project/SKILL.md
 detectkit/cli/commands/__init__.py