You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Gaps — Factors that are missing or only partially supported by current repo signals.
35
52
# Note: Base the result on explicit factor rules, not free-form judgment.
@@ -39,55 +56,47 @@ commands:
39
56
gaps:
40
57
- factor: config
41
58
status: partial
42
-
message: Config signals exist, but no explicit env contract file was detected. Add .env.example, .env.sample, or .env.template when runtime configuration is required.
59
+
message: Found config-bearing repo assets in deploy.yml, but no canonical checked-in config contract is declared yet.
1. Before each session, make sure `dev.kit` itself is up to date, then run `dev.kit`. Refresh focused layers with `dev.kit repo` or `dev.kit agent` after repo changes.
13
-
2. Read `.rabbit/context.yaml` first. It is the machine contract for refs, commands, dependencies, manifests, and gaps.
14
-
3. Read only the refs, manifests, dependency context, and explicitly referenced paths from `context.yaml`. Avoid broad filesystem scans.
15
-
4. Prefer manifests and repo-declared commands over implementation guesses. Do not edit generated `.rabbit/context.yaml` directly.
16
-
5. Fetch dynamic GitHub state with `gh` only when the current task needs issues, PRs, reviews, workflow runs, or alerts.
12
+
1. Make sure `dev.kit` itself is current, then run `dev.kit`.
13
+
2. Read `.rabbit/context.yaml` first when it exists.
14
+
3. Read the highest-priority refs and manifests that `context.yaml` points to.
15
+
4. Run `dev.kit repo` after repo changes or when context is missing or stale.
17
16
18
-
### Dependency context
17
+
##Operating rules
19
18
20
-
When a dependency entry points to another repo, treat that repo as its own context boundary. Prefer the dependency repo’s `.rabbit/context.yaml`; if it is missing in a local checkout, run `dev.kit repo` from that dependency repo before reading its implementation files.
21
-
22
-
For manifest backend traces, read the manifest first, then the traced backend path or docs listed under that manifest entry. Use live GitHub lookups only when local dependency context is unavailable or stale.
23
-
24
-
### Gap repair loop
25
-
26
-
For each gap, read its evidence in `context.yaml`, identify the repo-owned source asset that should declare the missing contract, patch that source asset, then rerun `dev.kit repo`. Repeat until the gap is resolved or clearly document why the repo intentionally cannot cover it.
27
-
28
-
Do not patch generated context to hide a gap. Fix docs, example env files, manifests, workflows, package scripts, Dockerfiles, or other primary repo assets so the next context refresh can detect the improvement.
29
-
30
-
- config (partial): Config signals exist, but no explicit env contract file was detected. Add .env.example, .env.sample, or .env.template when runtime configuration is required.
19
+
- treat `.rabbit/context.yaml` as generated repo evidence, not hand-authored guidance
20
+
- prefer repo-declared commands and manifests over guessed behavior
21
+
- keep durable workflow guidance in repo-owned docs, especially `docs/references/agent-dev-workflow.md`
22
+
- when a gap appears, repair the owning repo asset and rerun `dev.kit repo`
23
+
- use live GitHub data only when the task needs issues, PRs, reviews, workflow runs, or alerts
31
24
32
25
## Workflow
33
26
34
-
Use these repo-derived steps as the default operating path. Adapt them to the current agent role instead of forcing a single development lifecycle onto every task.
0 commit comments