orama-repo-rules

Loads mandatory repo-specific behavioral rules and syncs the canonical skill before code changes.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill orama-repo-rules-diazmelgarejo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orama-repo-rules
Source: https://github.com/diazMelgarejo/orama-system/tree/main/bin/orama-system/skills/orama-repo-rules
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill orama-repo-rules-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors to the orama-system repository risk repeating past mistakes or violating repo-specific conventions because the rules derived from prior bugs are scattered across docs. This Skill ensures every session starts by loading the canonical ruleset and a safely synced repository state before any code change. ## Core Features & Use Cases - Canonical Skill Loading: Acts as a thin wrapper that resolves the repo root at runtime and loads the canonical SKILL.md rather than duplicating behavior. - Safe Repository Sync: Checks tracking branch and worktree cleanliness, then performs git pull --ff-only, or falls back to a stash-pull-pop workflow when the worktree is dirty. - Drift Protection: Refuses git reset --hard or force-push on main, reporting drift instead when fast-forward is impossible. - Use Case: When starting a new coding session in the orama-system repo, invoke this Skill so the agent reads docs/LESSONS.md-derived rules and syncs the repo safely before editing any file. ## Quick Start Ask the agent to load the orama repo rules and sync the repository before making any code change in this project.

Frequently Asked Questions about orama-repo-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I load repo-specific coding rules before making changes?

Invoke this Skill at session start; it resolves the repository root at runtime and loads the canonical SKILL.md containing the mandatory ruleset. The wrapper never duplicates behavior, so the canonical file remains the single source of truth.

How do I safely sync a git repo before editing files?

The Skill runs git fetch and checks branch status, then performs git pull --ff-only when the worktree is clean and tracking origin. If the worktree is dirty, it follows a stash, pull --ff-only, pop, commit, push sequence from the git-history-surgery reference.

What happens when the branch cannot fast-forward?

When the branch is not tracking origin or fast-forward is impossible, the Skill reports drift instead of forcing a sync. It explicitly prohibits git reset --hard and force-pushing main to prevent history destruction.

Does this Skill work on Windows PowerShell?

Yes, but it requires explicit UTF-8 configuration before reading or writing skill files. The Skill documents setting Console input/output encodings, $OutputEncoding, and PYTHONUTF8 to avoid encoding corruption.

When should I not use these repo rules?

Do not use this Skill for general coding questions unrelated to the orama-system repository's own history and conventions. It is scoped strictly to sessions and changes within this specific repo.