oris-skills 2.2.1 → 2.2.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: oris-flow
3
- description: The one Oris skill - read the intent, pick ONE route, apply it in the same chat. Use for /oris-flow and whenever the user wants to set up a repo for agents, start a project, understand or define behavior, write acceptance criteria, plan, implement, fix a bug, verify criteria, handle a spec change, run a work loop (fix until green, repeat until verified), review architecture, update task docs, or asks how Oris works.
3
+ description: The one Oris skill - read the intent, pick ONE route, apply it in the same chat. Use for /oris-flow and whenever the user wants to set up a repo for agents, start a project, understand or define behavior, write acceptance criteria, plan, implement, fix a bug, verify criteria, handle a spec change, run a work loop (fix until green, repeat until verified), review architecture, update task docs, commit changes, open a pull request, or asks how Oris works.
4
4
  ---
5
5
 
6
6
  # Oris Flow — the router
@@ -32,6 +32,8 @@ Match the desired outcome to ONE route, then apply its reference:
32
32
  | loop | repeat work until verified — fix until green, step through a plan | `skills/oris-flow/references/loop.md` |
33
33
  | architecture | review architecture, find deepening/refactor opportunities | `skills/oris-flow/references/architecture.md` |
34
34
  | docs | update task docs after a change | `skills/oris-flow/references/docs.md` |
35
+ | commit | commit changes with the Oris standard — map fresh, Conventional Commits, work item linked | `skills/oris-flow/references/commit.md` |
36
+ | pr | open or update a pull request, English title/description linked to the work item | `skills/oris-flow/references/pr.md` |
35
37
  | help | how Oris works, install, update, troubleshooting | `skills/oris-flow/references/help.md` |
36
38
 
37
39
  ## Precedence (the calls that look ambiguous)
@@ -47,10 +49,14 @@ Match the desired outcome to ONE route, then apply its reference:
47
49
  5. CHECK once → verify. Repeat-until-verified → loop.
48
50
  6. EMPTY directory or from-scratch intent → new. Existing repo without
49
51
  `.oris-flow/manifest.json` → recommend setup first; respect the user's choice.
52
+ 7. COMMIT staged/working changes with the standard → commit. OPEN or update a pull request
53
+ → pr. Neither writes product code — they package and publish what implement/fix produced.
50
54
 
51
55
  ## Menu (low confidence)
52
56
 
53
- ASK "What do you want to do?" localized to `uiLanguage`, options:
57
+ ASK "What do you want to do?" in the user's language. This menu exceeds every
58
+ question tool's option cap — present it as a plain-text lettered list (the deliberate
59
+ fallback in `references/conventions.md` `## Questions`), options:
54
60
 
55
61
  - Setup repository
56
62
  - New project from scratch
@@ -63,6 +69,8 @@ ASK "What do you want to do?" localized to `uiLanguage`, options:
63
69
  - Loop: repeat until verified
64
70
  - Architecture review
65
71
  - Update docs
72
+ - Commit changes
73
+ - Open a pull request
66
74
  - Help
67
75
  - Explain the options / Spiega le opzioni
68
76
 
@@ -0,0 +1,45 @@
1
+ # Commit
2
+
3
+ Turn staged or working changes into one clean commit — map fresh, message in English,
4
+ work item linked. NEVER commit without showing the message and getting a yes.
5
+
6
+ RULES: `references/conventions.md`. DevOps config: `references/devops.md`.
7
+
8
+ ## Before the commit
9
+
10
+ 1. FRESHEN the map: `npx oris-skills flow scan --repository-root <repo> --check`. Stale →
11
+ refresh ONLY the changed areas (`--area <section>`) and stage `.oris-flow/` with the change.
12
+ 2. READ the diff (`git status`, `git diff --staged`) to know what actually changed.
13
+ 3. RESOLVE the work item id from context — current branch, the active task doc, or the
14
+ DevOps provider's active items. Unsure → ASK once for the id; never invent one.
15
+
16
+ ## Compose (always English)
17
+
18
+ - TYPE from Conventional Commits: `feat` | `fix` | `chore` | `docs` | `refactor` | `test`
19
+ | `perf` | `build` | `ci`. Pick from the diff, not the chat.
20
+ - SUBJECT imperative, ≤72 chars, no trailing period. Optional `(scope)`.
21
+ - BODY only when it adds signal: what and why, not how.
22
+ - FOOTER: the work item via the provider `workItemSyntax` (default `#{id}`), on its own line.
23
+
24
+ ## Gate (never skipped)
25
+
26
+ SHOW the full message + the files it will commit (code + refreshed map). ASK:
27
+ commit | edit message | cancel. ON commit → `git commit`; NEVER `--no-verify`.
28
+
29
+ ## After
30
+
31
+ - SUMMARIZE the commit (hash, subject, work item).
32
+ - OFFER a pull request (`skills/oris-flow/references/pr.md`) or stop. NEVER auto-open one.
33
+
34
+ ## Never
35
+
36
+ - Commit before the message and file list are shown and confirmed.
37
+ - Write the message in any language but English.
38
+ - Invent a work item id, or bypass hooks with `--no-verify`.
39
+ - Refresh confirmed map sections, or scan-rewrite areas the diff did not touch.
40
+
41
+ ## Done when
42
+
43
+ - [ ] Map checked, and refreshed in place only where the diff touched.
44
+ - [ ] English Conventional message with the work item linked, confirmed at the gate.
45
+ - [ ] Commit made without `--no-verify`; next step offered, not auto-run.
@@ -16,7 +16,7 @@ details on request.
16
16
  | Loop status | `npx oris-skills loop chat --action status` / `npx oris-skills loop list` |
17
17
  | Skill missing after install | Reload the agent; check `~/.oris/oris-skills/` exists; re-run install with `--force`. |
18
18
  | Hook not firing | `npx oris-skills loop verify --temp` self-checks the runtime; `npx oris-skills loop bootstrap` re-arms repo hooks. |
19
- | Change language / test profiles | `/oris-flow` → Setup → language & profiles (settings live in `~/.oris/settings.json`). |
19
+ | Change document language / chat verbosity | `/oris-flow` → Setup (settings live in `.oris-flow/settings.json`). |
20
20
  | Ultra-short answers | `/oris-flow` → Setup → set `responseStyle: caveman` — chat shrinks to maximum token density; documents stay complete. |
21
21
  | Edit a loop's behavior | Edit the files in `.oris-flow/loops/{slug}/prompts/` — the next pass obeys them. |
22
22
 
@@ -0,0 +1,44 @@
1
+ # Pull Request
2
+
3
+ Open or update a pull request whose title and description are English and linked to the
4
+ work item. NEVER open or update a PR without showing it and getting a yes.
5
+
6
+ RULES: `references/conventions.md`. DevOps config: `references/devops.md`.
7
+
8
+ ## Before
9
+
10
+ 1. ENSURE the branch is pushed and its commits follow the commit standard
11
+ (`skills/oris-flow/references/commit.md`); uncommitted work remains → route there first.
12
+ 2. READ the commit range to summarize the actual change, not the intent.
13
+ 3. RESOLVE the work item id (branch, task doc, or DevOps provider) — unsure → ASK once.
14
+
15
+ ## Compose (always English)
16
+
17
+ - TITLE: one Conventional line, same grammar as a commit subject.
18
+ - DESCRIPTION: a short **Summary** (what changed and why), a **Verification** line
19
+ (how it was proven), and the work item via the provider `workItemSyntax` (default `#{id}`).
20
+ - KEEP secrets out — mask anything sensitive as `***` (`references/conventions.md` `## Gates`).
21
+
22
+ ## Gate (never skipped)
23
+
24
+ SHOW the title + description + target branch. ASK: open PR | edit | cancel.
25
+ ON open → create via the provider (Azure DevOps MCP `oris-devops`, or `gh` for GitHub)
26
+ read from `references/devops.md`. Missing provider auth → say so; never guess credentials.
27
+
28
+ ## After
29
+
30
+ - SUMMARIZE: PR link/number, target branch, work item.
31
+ - RECOMMEND verify (`skills/oris-flow/references/verify.md`) when criteria exist.
32
+ NEVER merge automatically.
33
+
34
+ ## Never
35
+
36
+ - Open or update a PR before the title and description are shown and confirmed.
37
+ - Write the title or description in any language but English.
38
+ - Invent a work item id, store credentials, or merge without being asked.
39
+
40
+ ## Done when
41
+
42
+ - [ ] Branch pushed and commits follow the commit standard.
43
+ - [ ] English title + description with the work item linked, confirmed at the gate.
44
+ - [ ] PR opened/updated via the configured provider; merge never automatic.
@@ -18,7 +18,7 @@ refreshing. THEN ask ONE question with these options:
18
18
  - review stale sections
19
19
  - show summary (no writes)
20
20
  - recreate from scratch
21
- - language & profiles → Local Preferences below; touches only `~/.oris/settings.json`
21
+ - preferences → Local Preferences below; touches only `.oris-flow/settings.json`
22
22
  - clean runtime → preview with `npx oris-skills flow clean-runtime --repository-root <repo> --dry-run`, confirm, run without `--dry-run`
23
23
 
24
24
  ELSE → create from scratch.
@@ -29,9 +29,13 @@ ELSE → create from scratch.
29
29
  2. SCAN: `npx oris-skills flow scan --repository-root <repo> --json` — deterministic
30
30
  baseline: `projectType`, stacks, commands (with confidence), sections, `truncated`
31
31
  flag. Scan output = draft evidence, not truth.
32
- 3. IF `truncated: true` → say so; large monorepos may need per-area subagent scans.
33
- 4. ADD parallel subagent scans (docs, frontend, backend/data, tests/build, local
34
- skills/rules) only when the baseline leaves real gaps.
32
+ 3. IF `truncated: true` → say so, then per-area subagent scans are REQUIRED, not optional.
33
+ 4. FAN OUT parallel subagent scans (docs, frontend, backend/data, tests/build, local
34
+ skills/rules) by DEFAULT whenever the repo has more than one of those areas —
35
+ entering setup is the user's request to spawn (`references/conventions.md`
36
+ `## Subagents`). SKIP only when the repo is small enough that the baseline already
37
+ answers every §2 decision — say you skipped and why. No agent tool on the platform →
38
+ same scans inline, sequentially.
35
39
 
36
40
  ## 2. Present findings, decide one at a time
37
41
 
@@ -45,8 +49,6 @@ Then WALK decisions ONE per turn — short explainer first, recommended answer f
45
49
  project docs. Record in `setup.tasksRoot`.
46
50
  - **Verify commands** — show detected build+test commands; user confirms or corrects →
47
51
  mark `confirmed`. They feed implement, verify, and loop VERIFIER; unconfirmed = a guess.
48
- - **Refresh policy** (manual | monthly | after refactor | after test-layout change) —
49
- advisory only, never a scheduler.
50
52
  - **Version control for `.oris-flow/`** — commit (team default) or gitignore. Task docs
51
53
  follow the same choice.
52
54
 
@@ -78,10 +80,10 @@ ON explicit confirmation per file → scaffold the missing ones minimal.
78
80
 
79
81
  ## Local Preferences
80
82
 
81
- 1. READ `~/.oris/settings.json` (defaults in `references/settings.md`).
82
- 2. ASK what to change: uiLanguage | artifactLanguage | responseStyle (standard |
83
- caveman — maximum token density in chat) | default test profile | profiles.
84
- 3. SHOW masked summary (passwords `***`), CONFIRM, write ONLY the settings file.
83
+ 1. READ `.oris-flow/settings.json` (defaults in `references/settings.md`).
84
+ 2. ASK what to change: artifactLanguage (document language, default `en`) | responseStyle
85
+ (standard | caveman — maximum token density in chat).
86
+ 3. SHOW summary, CONFIRM, write ONLY the settings file.
85
87
 
86
88
  ## Never
87
89