Codifies a project's real code conventions into cached per-language pattern files for ORC executors.
npx skills add https://github.com/azure-id/orc --skill orc-pattern-azure-id
Please help me install this Agent Skill. Skill: orc-pattern Source: https://github.com/azure-id/orc/tree/main/templates/skills/orc-pattern Command: npx skills add https://github.com/azure-id/orc --skill orc-pattern-azure-id
.claude/orc/patterns/<lang>-pattern.md files covering React, Next.js, Vue, Angular, FastAPI, Django, NestJS, Express, Go, and Postgres, reused by every future ORC run with drift detection and --refresh support. - Subagent-based codification: Dispatches a dedicated codifier subagent to scan representative files, keeping the orchestrator's context lean, with consent-gated scanning and a language-agnostic fallback when declined. - Use Case: Before ORC executes tasks in a FastAPI + React monorepo, run the pattern codifier once so every executor writes endpoints and components that follow the project's actual router layout, naming, and validation style. ## Quick Start Ask the agent to run /orc-pattern to learn and cache this project's code conventions for all detected languages.High-intent search queries and answers about installing and using this skill.
Run /orc-pattern to codify your project's conventions. It scans the most-recently-modified files per detected language, reconciles them against a generic playbook, and caches the result in .claude/orc/patterns/ for every future ORC run.
It ships playbooks for React, Next.js, Vue, Angular, FastAPI, Django, NestJS, Express, Go, and Postgres data-access. Postgres is cross-cutting and co-applies with the framework pattern when a task touches the data layer.
Conventions like folder layout and naming always defer to the project, while security and correctness invariants such as parameterized queries and no leaked secrets are always enforced. Conflicts are flagged to the user once rather than silently resolved.
Yes. A cheap structural fingerprint of representative files detects drift, and a drifted cache is automatically re-codified on the next run. You can also force regeneration at any time with /orc-pattern --refresh.
Yes. Set pattern_findings to off or decline at the prompt, and executors fall back to a language-agnostic path: they apply the universal security invariants and imitate the neighboring files they already read, with nothing cached.
shakhovskiya-createDetect project languages and frameworks via file extensions and manifests.
MarcoBolsaValidates work against Markdown checklists with pass, fail, and partial verdicts.
jikig-aiScan git-diff-selected source files with semgrep for vulnerability patterns.
foomakersValidate codebase quality against linting, type-checking, and test gates.