Instructions file GitHub Copilot
Product names differ across the matrix CSV, product codes, slugs, and docs. Matching stays heuristic and alias coverage is iterative.
Instructions file GitHub Copilot
Product names differ across the matrix CSV, product codes, slugs, and docs. Matching stays heuristic and alias coverage is iterative.
Instructions file GitHub Copilot
Use when working on SQLite schema, database initialization, WAL mode, FTS5 triggers, or table definitions.
Instructions file GitHub Copilot
Released databases carry dbmeta provenance stamped in CI and surfaced by runtime entrypoints.
Instructions file GitHub Copilot
Use descriptive prose filenames for instruction files, tasks, and briefings so the purpose is obvious from a directory listing.
Instructions file GitHub Copilot
Routing file for extraction/data work. Follow the narrow instruction files listed here instead of growing this file again.
Instructions file GitHub Copilot
Extraction scripts rebuild their tables deterministically. Delete or drop first; do not mutate incremental state in place.
Instructions file GitHub Copilot
Every extractor entrypoint must run its side effects only under import.meta.main. Top-level db.ts imports still open a real DB connection, so tests must import extractors safely.
Instructions file GitHub Copilot
GitHub API calls in this repo must be authenticated. Unauthenticated calls hit the 60 req/hr (or lower, unauthenticated raw.githubusercontent.com) limit fast and are the recurring cause of release/extraction failures.
Instructions file GitHub Copilot
Meta-rule for writing agent instruction files: one topic per file, smallest honest scope, and pointers instead of duplicated prose.
Instructions file GitHub Copilot
Every PR that implements an issue must auto-close it via 'Closes #N'; partial landings spawn follow-up issues before merge.
Instructions file GitHub Copilot
LLM-targeted instruction files are excluded from markdownlint so authoring rules for human docs do not distort agent-facing guidance.
Instructions file GitHub Copilot
In a checkout, the resolved ros-help.db is untrusted until verified; the latest CI release DB is the grounding source of truth.
Instructions file GitHub Copilot
Version bumps and CHANGELOG promotion are a manual, human step for every release channel. CI must not reintroduce an auto-bump/auto-commit job.
Instructions file GitHub Copilot
Markdown code blocks must be fenced and language-tagged; use routeros for RouterOS CLI and text for plain output.
Instructions file GitHub Copilot
Routing file for MCP/query/TUI work. The actual rules live in the narrow instruction files listed here.
Instructions file GitHub Copilot
Tool descriptions should teach agents how to navigate the surface: workflow arrows, empty-result hints, boundaries, and result-budget cues.
Instructions file GitHub Copilot
Instructions for tikoci/rosetta, a project described as: MCP Server with RouterOS docs + commands + products + changelogs, using SQLite-as-RAG, sourced from MikroTik.
Instructions file GitHub Copilot
How Copilot and CodeRabbit reviews manifest on a rosetta PR, why each looks different from a gh point of view, and what 'wrapping a PR' actually requires.
Instructions file GitHub Copilot
Shared behavior belongs in query.ts so MCP and browse inherit it. Adapter-only heuristics are a smell.
Instructions file GitHub Copilot
Published releases go through the GitHub Actions Release workflow. Do not document or rely on stale local release commands.
Instructions file GitHub Copilot
Instructions for tikoci/rosetta: The republishassets workflow input is for GitHub Release assets and OCI tags only.
Instructions file GitHub Copilot
Instructions for tikoci/rosetta, a project described as: MCP Server with RouterOS docs + commands + products + changelogs, using SQLite-as-RAG, sourced from MikroTik.
Instructions file GitHub Copilot
RouterOS skills are community-created supplemental guides, not official MikroTik docs. Preserve the attribution boundary everywhere they surface.
Instructions file GitHub Copilot
Pointer for the work-tracking split: GitHub issues are commitments, briefings are research, backlog is the loose/thinking-first layer, tasks/ is a frozen archive.