marcos-ai-bootstrap 0.1.7 → 0.1.9
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.
- package/README.md +6 -3
- package/package.json +1 -1
- package/src/.agents/skills/implement/SKILL.md +18 -0
- package/src/.agents/skills/initialize/SKILL.md +7 -7
- package/src/.agents/skills/planner/SKILL.md +17 -0
- package/src/.agents/skills/{pr → pull-request}/SKILL.md +2 -2
- package/src/.agents/skills/watch-ci/SKILL.md +17 -0
- package/src/.claude/skills/implement/SKILL.md +18 -0
- package/src/.claude/skills/initialize/SKILL.md +4 -4
- package/src/.claude/skills/planner/SKILL.md +17 -0
- package/src/.claude/skills/{pr → pull-request}/SKILL.md +2 -2
- package/src/.claude/skills/watch-ci/SKILL.md +17 -0
- package/src/.codex/agents/code-codex.toml +1 -1
- package/src/.codex/agents/docs-codex.toml +1 -1
- package/src/.codex/agents/explorer-codex.toml +1 -1
- package/src/.codex/agents/infra-codex.toml +1 -1
- package/src/.codex/agents/investigate-codex.toml +1 -1
- package/src/.codex/agents/log-reader-codex.toml +1 -1
- package/src/.codex/agents/planner-codex.toml +1 -1
- package/src/.codex/agents/planner-discovery-codex.toml +1 -1
- package/src/.codex/agents/test-runner-codex.toml +1 -1
- package/src/.codex/agents/triage-codex.toml +1 -1
- package/src/.github/skills/implement/SKILL.md +18 -0
- package/src/.github/skills/initialize/SKILL.md +4 -4
- package/src/.github/skills/planner/SKILL.md +17 -0
- package/src/.github/skills/{pr → pull-request}/SKILL.md +2 -2
- package/src/.github/skills/watch-ci/SKILL.md +17 -0
- package/src/HUMAN.md +1 -1
- package/src/MARCOS-AI-BOOTSTRAP.md +4 -4
package/README.md
CHANGED
|
@@ -120,10 +120,13 @@ major version:
|
|
|
120
120
|
|
|
121
121
|
| Commit type | Result (pre-1.0) |
|
|
122
122
|
|---|---|
|
|
123
|
-
| `fix:` / `feat:`
|
|
123
|
+
| `fix:` / `feat:` | patch (e.g. `0.1.0` → `0.1.1`) |
|
|
124
124
|
| `feat!:` or a `BREAKING CHANGE:` footer | minor (e.g. `0.1.0` → `0.2.0`) |
|
|
125
125
|
| any commit with a `Release-As: X.Y.Z` footer | forces exactly that version |
|
|
126
126
|
|
|
127
|
+
These commit types do **not** trigger a release on their own: `refactor:`, `chore:`,
|
|
128
|
+
`docs:`, `perf:`, `test:`, `ci:`, `build:`, `style:`. (`bump-patch-for-minor-pre-major`
|
|
129
|
+
only sizes a bump that is already triggered — it does not make these types releasable.)
|
|
130
|
+
|
|
127
131
|
Cut `1.0.0` with a `Release-As: 1.0.0` commit when the API is stable; after that, standard
|
|
128
|
-
SemVer applies (`feat:` → minor, breaking → major).
|
|
129
|
-
`ci:`) won't create a Release PR on their own.
|
|
132
|
+
SemVer applies (`feat:` → minor, breaking → major).
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "marcos-ai-bootstrap",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.9",
|
|
4
4
|
"description": "Materialise the AI-Bootstrap agent/skill network (Claude Code, Codex, GitHub Copilot CLI) into any repository from the command line.",
|
|
5
5
|
"bin": {
|
|
6
6
|
"marcos-ai-bootstrap": "src/bin/ai-bootstrap.js"
|
|
@@ -5,6 +5,24 @@ description: Execute an existing plan from documents/plans/ (path passed by the
|
|
|
5
5
|
|
|
6
6
|
You are the implement orchestrator. Execute a written plan phase by phase.
|
|
7
7
|
|
|
8
|
+
## Mandatory delegation contract
|
|
9
|
+
|
|
10
|
+
This skill is an orchestrator, not an implementer.
|
|
11
|
+
|
|
12
|
+
Before executing a phase:
|
|
13
|
+
|
|
14
|
+
1. Read the plan only to identify its designated agent for that phase.
|
|
15
|
+
2. Verify that the matching Codex agent can be invoked through the active agent-delegation mechanism.
|
|
16
|
+
3. Invoke that agent with the complete phase objective, relevant files, acceptance criteria, and required prior context.
|
|
17
|
+
4. Use the delegated agent's result as the basis for phase completion and verification.
|
|
18
|
+
|
|
19
|
+
If the designated agent cannot be invoked:
|
|
20
|
+
|
|
21
|
+
- Stop immediately.
|
|
22
|
+
- State that the designated agent is unavailable in the current runtime.
|
|
23
|
+
- Do not implement, modify files, or complete the phase as a substitute.
|
|
24
|
+
- Do not silently substitute a different agent or perform the phase yourself.
|
|
25
|
+
|
|
8
26
|
## Input
|
|
9
27
|
|
|
10
28
|
The user provides a path to a plan file, e.g. `documents/plans/20260622-ui-bugs.md`. Read the plan and extract:
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: initialize
|
|
3
|
-
description: One-time environment reconciliation. First wires this tool's instruction file to the shipped MARCOS-AI-BOOTSTRAP.md rules (appending an @-include, never overwriting; creating the file if absent). Discovers applicable MCP servers and, with user approval, installs and wires them into the infra/planner agents; discovers where plan documents actually live and, after user confirmation, wires the planner/implement/docs agents to that location; scans past PRs, branch names, and commit history and, after user confirmation, customises the `
|
|
3
|
+
description: One-time environment reconciliation. First wires this tool's instruction file to the shipped MARCOS-AI-BOOTSTRAP.md rules (appending an @-include, never overwriting; creating the file if absent). Discovers applicable MCP servers and, with user approval, installs and wires them into the infra/planner agents; discovers where plan documents actually live and, after user confirmation, wires the planner/implement/docs agents to that location; scans past PRs, branch names, and commit history and, after user confirmation, customises the `pull-request` skill's convention profile; then always prompts the user to choose the model for each tier/role (pre-selecting the current model, or the closest available match when it is unavailable) and rewrites the agent files. Never commits.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
You are the initialize orchestrator. Reconcile this repo's agent network with the current environment in the phases below. This skill only edits agent and skill files, the tool's instruction entry-point, and MCP config; it never touches source code and never commits.
|
|
@@ -41,9 +41,9 @@ The full agent rules ship as `MARCOS-AI-BOOTSTRAP.md` at the repo root. Ensure t
|
|
|
41
41
|
|
|
42
42
|
| Tier | Model ID |
|
|
43
43
|
|---|---|
|
|
44
|
-
| High | `gpt-5.
|
|
45
|
-
| Standard | `gpt-5.
|
|
46
|
-
| Fast | `gpt-5.
|
|
44
|
+
| High | `gpt-5.6-sol` |
|
|
45
|
+
| Standard | `gpt-5.6-terra` |
|
|
46
|
+
| Fast | `gpt-5.6-luna` |
|
|
47
47
|
|
|
48
48
|
## Phase 3 - Documentation location reconciliation
|
|
49
49
|
|
|
@@ -55,7 +55,7 @@ The full agent rules ship as `MARCOS-AI-BOOTSTRAP.md` at the repo root. Ensure t
|
|
|
55
55
|
|
|
56
56
|
## Phase 4 - PR & contribution convention discovery
|
|
57
57
|
|
|
58
|
-
Customise the `
|
|
58
|
+
Customise the `pull-request` skill so it matches how THIS repository actually works, learned from its own history rather than assumed defaults.
|
|
59
59
|
|
|
60
60
|
1. Gather evidence of the repo's conventions:
|
|
61
61
|
- **Past PRs** - `gh pr list --state merged --limit 50 --json number,title,headRefName,body`. Infer PR-title patterns (Conventional Commits, ticket prefixes like `[ABC-123]`, sentence vs lower case), branch-name patterns (prefixes, separators, casing), and PR-body structure (required sections, checklists).
|
|
@@ -64,8 +64,8 @@ Customise the `pr` skill so it matches how THIS repository actually works, learn
|
|
|
64
64
|
- **Repo settings** - `gh repo view --json defaultBranchRef,mergeCommitAllowed,squashMergeAllowed,rebaseMergeAllowed` for the default branch and allowed merge methods.
|
|
65
65
|
2. Synthesise a concise convention profile: branch-name rules, commit-message rules, PR-title rules, PR-body/template rules, and any release-automation constraints. Prefer the dominant observed pattern; where history is sparse or inconsistent, fall back to the general Conventional Commits defaults and say so explicitly.
|
|
66
66
|
3. Present the inferred profile to the user for confirmation or edits. Do not rewrite the skill without confirmation.
|
|
67
|
-
4. On confirmation, rewrite ONLY the "Repository conventions" block of `.agents/skills/
|
|
68
|
-
5. Report the resolved convention profile and confirm the `
|
|
67
|
+
4. On confirmation, rewrite ONLY the "Repository conventions" block of `.agents/skills/pull-request/SKILL.md` - the text between the `<!-- CONVENTIONS:START -->` and `<!-- CONVENTIONS:END -->` markers - with the confirmed profile. Leave the rest of the skill untouched.
|
|
68
|
+
5. Report the resolved convention profile and confirm the `pull-request` skill was updated.
|
|
69
69
|
|
|
70
70
|
## Guardrails
|
|
71
71
|
- Never commit or push - you edit agent and skill files and MCP config; the user commits.
|
|
@@ -5,6 +5,23 @@ description: Formalise the two-stage planning flow. Stage 1 runs planner-discove
|
|
|
5
5
|
|
|
6
6
|
You are the planner orchestrator. Drive the two-stage planning flow.
|
|
7
7
|
|
|
8
|
+
## Mandatory delegation contract
|
|
9
|
+
|
|
10
|
+
This skill is an orchestrator, not a planner.
|
|
11
|
+
|
|
12
|
+
Before researching, asking substantive questions, or producing an outline:
|
|
13
|
+
|
|
14
|
+
1. Verify that `planner-discovery-codex` can be invoked through the active Codex agent-delegation mechanism.
|
|
15
|
+
2. Invoke `planner-discovery-codex`, passing the complete user request and relevant context.
|
|
16
|
+
3. Use only that agent's Stage 1 result as the basis for the user-facing outline.
|
|
17
|
+
|
|
18
|
+
If the agent cannot be invoked:
|
|
19
|
+
|
|
20
|
+
- Stop immediately.
|
|
21
|
+
- State that `planner-discovery-codex` is unavailable in the current runtime.
|
|
22
|
+
- Do not inspect the repository, browse, ask discovery questions, or create an outline as a substitute.
|
|
23
|
+
- Do not silently perform Stage 1 yourself.
|
|
24
|
+
|
|
8
25
|
## Stage 1 - Discovery & Outline
|
|
9
26
|
|
|
10
27
|
Invoke `planner-discovery-codex` with the user's task description and any relevant context. That agent will:
|
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
---
|
|
2
|
-
name:
|
|
2
|
+
name: pull-request
|
|
3
3
|
description: Open a pull request that follows this repository's conventions for branch names, commit messages, and PR titles and bodies. Verifies you are on a working branch, checks and repairs the branch/commits/title against the active convention profile, pushes, and opens the PR with the GitHub CLI. Never merges the PR.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are the
|
|
6
|
+
You are the pull-request orchestrator. Open a pull request that conforms to this repository's contribution conventions, then hand off to the user to merge. Never merge the PR yourself and never push to the default branch.
|
|
7
7
|
|
|
8
8
|
## Convention profile
|
|
9
9
|
|
|
@@ -5,6 +5,23 @@ description: Watch a GitHub Actions workflow, auto-fix failures via the Codex ag
|
|
|
5
5
|
|
|
6
6
|
You are the watch-ci orchestrator. Drive the CI fix loop until the target workflow is green.
|
|
7
7
|
|
|
8
|
+
## Mandatory delegation contract
|
|
9
|
+
|
|
10
|
+
This skill is an orchestrator, not a diagnostician, triager, investigator, or implementer.
|
|
11
|
+
|
|
12
|
+
Before resolving the target, inspecting CI, or entering the fix loop:
|
|
13
|
+
|
|
14
|
+
1. Verify that `log-reader-codex`, `triage-codex`, `investigate-codex`, and `code-codex` can be invoked through the active Codex agent-delegation mechanism.
|
|
15
|
+
2. Invoke each agent only for its corresponding step in the prescribed fix loop, passing all relevant prior outputs and context.
|
|
16
|
+
3. Use only the delegated agents' outputs as the basis for diagnosis, triage, investigation, and remediation.
|
|
17
|
+
|
|
18
|
+
If a required agent cannot be invoked:
|
|
19
|
+
|
|
20
|
+
- Stop immediately.
|
|
21
|
+
- State that the unavailable agent is unavailable in the current runtime.
|
|
22
|
+
- Do not inspect CI logs, diagnose, triage, investigate, or apply a fix as a substitute.
|
|
23
|
+
- Do not silently perform a delegated pipeline step yourself.
|
|
24
|
+
|
|
8
25
|
## Target resolution
|
|
9
26
|
|
|
10
27
|
Parse the optional input argument:
|
|
@@ -5,6 +5,24 @@ description: Execute an existing plan from documents/plans/ (path passed by the
|
|
|
5
5
|
|
|
6
6
|
You are the implement orchestrator. Execute a written plan phase by phase.
|
|
7
7
|
|
|
8
|
+
## Mandatory delegation contract
|
|
9
|
+
|
|
10
|
+
This skill is an orchestrator, not an implementer.
|
|
11
|
+
|
|
12
|
+
Before executing a phase:
|
|
13
|
+
|
|
14
|
+
1. Read the plan only to identify its designated agent for that phase.
|
|
15
|
+
2. Verify that the matching Claude Code agent can be invoked through the active agent-delegation mechanism.
|
|
16
|
+
3. Invoke that agent with the complete phase objective, relevant files, acceptance criteria, and required prior context.
|
|
17
|
+
4. Use the delegated agent's result as the basis for phase completion and verification.
|
|
18
|
+
|
|
19
|
+
If the designated agent cannot be invoked:
|
|
20
|
+
|
|
21
|
+
- Stop immediately.
|
|
22
|
+
- State that the designated agent is unavailable in the current runtime.
|
|
23
|
+
- Do not implement, modify files, or complete the phase as a substitute.
|
|
24
|
+
- Do not silently substitute a different agent or perform the phase yourself.
|
|
25
|
+
|
|
8
26
|
## Input
|
|
9
27
|
|
|
10
28
|
The user provides a path to a plan file, e.g. `documents/plans/20260622-ui-bugs.md`. Read the plan and extract:
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: initialize
|
|
3
|
-
description: One-time environment reconciliation. First wires this tool's instruction file to the shipped MARCOS-AI-BOOTSTRAP.md rules (appending an @-include, never overwriting; creating the file if absent). Discovers applicable MCP servers and, with user approval, installs and wires them into the infra/planner agents; discovers where plan documents actually live and, after user confirmation, wires the planner/implement/docs agents to that location; scans past PRs, branch names, and commit history and, after user confirmation, customises the `
|
|
3
|
+
description: One-time environment reconciliation. First wires this tool's instruction file to the shipped MARCOS-AI-BOOTSTRAP.md rules (appending an @-include, never overwriting; creating the file if absent). Discovers applicable MCP servers and, with user approval, installs and wires them into the infra/planner agents; discovers where plan documents actually live and, after user confirmation, wires the planner/implement/docs agents to that location; scans past PRs, branch names, and commit history and, after user confirmation, customises the `pull-request` skill's convention profile; then always prompts the user to choose the model for each tier/role (pre-selecting the current model, or the closest available match when it is unavailable) and rewrites the agent files. Never commits.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
You are the initialize orchestrator. Reconcile this repo's agent network with the current environment in the phases below. This skill only edits agent and skill files, the tool's instruction entry-point, and MCP config; it never touches source code and never commits.
|
|
@@ -55,7 +55,7 @@ The full agent rules ship as `MARCOS-AI-BOOTSTRAP.md` at the repo root. Ensure t
|
|
|
55
55
|
|
|
56
56
|
## Phase 4 — PR & contribution convention discovery
|
|
57
57
|
|
|
58
|
-
Customise the `
|
|
58
|
+
Customise the `pull-request` skill so it matches how THIS repository actually works, learned from its own history rather than assumed defaults.
|
|
59
59
|
|
|
60
60
|
1. Gather evidence of the repo's conventions:
|
|
61
61
|
- **Past PRs** — `gh pr list --state merged --limit 50 --json number,title,headRefName,body`. Infer PR-title patterns (Conventional Commits, ticket prefixes like `[ABC-123]`, sentence vs lower case), branch-name patterns (prefixes, separators, casing), and PR-body structure (required sections, checklists).
|
|
@@ -64,8 +64,8 @@ Customise the `pr` skill so it matches how THIS repository actually works, learn
|
|
|
64
64
|
- **Repo settings** — `gh repo view --json defaultBranchRef,mergeCommitAllowed,squashMergeAllowed,rebaseMergeAllowed` for the default branch and allowed merge methods.
|
|
65
65
|
2. Synthesise a concise convention profile: branch-name rules, commit-message rules, PR-title rules, PR-body/template rules, and any release-automation constraints. Prefer the dominant observed pattern; where history is sparse or inconsistent, fall back to the general Conventional Commits defaults and say so explicitly.
|
|
66
66
|
3. Present the inferred profile to the user for confirmation or edits. Do not rewrite the skill without confirmation.
|
|
67
|
-
4. On confirmation, rewrite ONLY the "Repository conventions" block of `.claude/skills/
|
|
68
|
-
5. Report the resolved convention profile and confirm the `
|
|
67
|
+
4. On confirmation, rewrite ONLY the "Repository conventions" block of `.claude/skills/pull-request/SKILL.md` — the text between the `<!-- CONVENTIONS:START -->` and `<!-- CONVENTIONS:END -->` markers — with the confirmed profile. Leave the rest of the skill untouched.
|
|
68
|
+
5. Report the resolved convention profile and confirm the `pull-request` skill was updated.
|
|
69
69
|
|
|
70
70
|
## Guardrails
|
|
71
71
|
- Never commit or push — you edit agent and skill files and MCP config; the user commits.
|
|
@@ -5,6 +5,23 @@ description: Formalise the two-stage planning flow. Stage 1 runs planner-discove
|
|
|
5
5
|
|
|
6
6
|
You are the planner orchestrator. Drive the two-stage planning flow.
|
|
7
7
|
|
|
8
|
+
## Mandatory delegation contract
|
|
9
|
+
|
|
10
|
+
This skill is an orchestrator, not a planner.
|
|
11
|
+
|
|
12
|
+
Before researching, asking substantive questions, or producing an outline:
|
|
13
|
+
|
|
14
|
+
1. Verify that `planner-discovery-claude` can be invoked through the active Claude Code agent-delegation mechanism.
|
|
15
|
+
2. Invoke `planner-discovery-claude`, passing the complete user request and relevant context.
|
|
16
|
+
3. Use only that agent's Stage 1 result as the basis for the user-facing outline.
|
|
17
|
+
|
|
18
|
+
If the agent cannot be invoked:
|
|
19
|
+
|
|
20
|
+
- Stop immediately.
|
|
21
|
+
- State that `planner-discovery-claude` is unavailable in the current runtime.
|
|
22
|
+
- Do not inspect the repository, browse, ask discovery questions, or create an outline as a substitute.
|
|
23
|
+
- Do not silently perform Stage 1 yourself.
|
|
24
|
+
|
|
8
25
|
## Stage 1 — Discovery & Outline
|
|
9
26
|
|
|
10
27
|
Invoke the `planner-discovery-claude` agent with the user's task description and any relevant context. That agent will:
|
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
---
|
|
2
|
-
name:
|
|
2
|
+
name: pull-request
|
|
3
3
|
description: Open a pull request that follows this repository's conventions for branch names, commit messages, and PR titles and bodies. Verifies you are on a working branch, checks and repairs the branch/commits/title against the active convention profile, pushes, and opens the PR with the GitHub CLI. Never merges the PR.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are the
|
|
6
|
+
You are the pull-request orchestrator. Open a pull request that conforms to this repository's contribution conventions, then hand off to the user to merge. Never merge the PR yourself and never push to the default branch.
|
|
7
7
|
|
|
8
8
|
## Convention profile
|
|
9
9
|
|
|
@@ -5,6 +5,23 @@ description: Watch a GitHub Actions workflow, auto-fix failures via the Claude C
|
|
|
5
5
|
|
|
6
6
|
You are the watch-ci orchestrator. Drive the CI fix loop until the target workflow is green.
|
|
7
7
|
|
|
8
|
+
## Mandatory delegation contract
|
|
9
|
+
|
|
10
|
+
This skill is an orchestrator, not a diagnostician, triager, investigator, or implementer.
|
|
11
|
+
|
|
12
|
+
Before resolving the target, inspecting CI, or entering the fix loop:
|
|
13
|
+
|
|
14
|
+
1. Verify that `log-reader-claude`, `triage-claude`, `investigate-claude`, and `code-claude` can be invoked through the active Claude Code agent-delegation mechanism.
|
|
15
|
+
2. Invoke each agent only for its corresponding step in the prescribed fix loop, passing all relevant prior outputs and context.
|
|
16
|
+
3. Use only the delegated agents' outputs as the basis for diagnosis, triage, investigation, and remediation.
|
|
17
|
+
|
|
18
|
+
If a required agent cannot be invoked:
|
|
19
|
+
|
|
20
|
+
- Stop immediately.
|
|
21
|
+
- State that the unavailable agent is unavailable in the current runtime.
|
|
22
|
+
- Do not inspect CI logs, diagnose, triage, investigate, or apply a fix as a substitute.
|
|
23
|
+
- Do not silently perform a delegated pipeline step yourself.
|
|
24
|
+
|
|
8
25
|
## Target resolution
|
|
9
26
|
|
|
10
27
|
Parse the optional input argument:
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
name = "code-codex"
|
|
2
2
|
description = "Use for well-scoped code changes — feature implementation, bug fixes, explicit refactors. Writes or updates tests first, makes the smallest change that satisfies the requirement, validates immediately. Does not touch documentation — delegate that to the docs agent after."
|
|
3
|
-
model = "gpt-5.
|
|
3
|
+
model = "gpt-5.6-terra"
|
|
4
4
|
model_reasoning_effort = "medium"
|
|
5
5
|
developer_instructions = """
|
|
6
6
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
name = "docs-codex"
|
|
2
2
|
description = "Use for documentation-only updates — root README, service-level README files, architecture notes, concept docs, plan documents. Runs after implementation is verified. Never modifies code, config, or infrastructure files."
|
|
3
|
-
model = "gpt-5.
|
|
3
|
+
model = "gpt-5.6-luna"
|
|
4
4
|
model_reasoning_effort = "medium"
|
|
5
5
|
developer_instructions = """
|
|
6
6
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
name = "explorer-codex"
|
|
2
2
|
description = "Use for read-only codebase research — finding files, tracing call paths, understanding architecture, locating where a symbol is defined or used. Makes no changes. Returns findings as a concise report."
|
|
3
|
-
model = "gpt-5.
|
|
3
|
+
model = "gpt-5.6-luna"
|
|
4
4
|
model_reasoning_effort = "medium"
|
|
5
5
|
developer_instructions = """
|
|
6
6
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
name = "infra-codex"
|
|
2
2
|
description = "Use for all infrastructure changes — Bicep templates, deployment pipeline YAML, IAC configuration. Never runs manual cloud CLI commands against shared environments. All changes go through files and pipelines."
|
|
3
|
-
model = "gpt-5.
|
|
3
|
+
model = "gpt-5.6-terra"
|
|
4
4
|
model_reasoning_effort = "high"
|
|
5
5
|
developer_instructions = """
|
|
6
6
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
name = "investigate-codex"
|
|
2
2
|
description = "Stage 2 of the bug fix pipeline. Analyzes diagnostics from log-reader, explores affected code, and pinpoints root cause. Does NOT implement — hands off to code agent for the fix."
|
|
3
|
-
model = "gpt-5.
|
|
3
|
+
model = "gpt-5.6-sol"
|
|
4
4
|
model_reasoning_effort = "medium"
|
|
5
5
|
developer_instructions = """
|
|
6
6
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
name = "log-reader-codex"
|
|
2
2
|
description = "Stage 1 of the bug fix pipeline. Gathers logs, error messages, and diagnostic context, then passes findings to the investigate agent. Read-only data collection — no code changes or analysis."
|
|
3
|
-
model = "gpt-5.
|
|
3
|
+
model = "gpt-5.6-luna"
|
|
4
4
|
model_reasoning_effort = "medium"
|
|
5
5
|
developer_instructions = """
|
|
6
6
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
name = "planner-codex"
|
|
2
2
|
description = "Stage 2 of planning. Invoke after the user has approved the outline from planner-discovery. Produces a full structured implementation plan written to documents/plans/. Does NOT implement — returns the plan for user approval before any code is written."
|
|
3
|
-
model = "gpt-5.
|
|
3
|
+
model = "gpt-5.6-sol"
|
|
4
4
|
model_reasoning_effort = "high"
|
|
5
5
|
developer_instructions = """
|
|
6
6
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
name = "planner-discovery-codex"
|
|
2
2
|
description = "Stage 1 of planning. Use first for any multi-phase or architecturally significant task. Asks clarifying questions, explores the codebase, and returns a concise outline for user approval. Does NOT write the full plan — invoke the planner agent after approval."
|
|
3
|
-
model = "gpt-5.
|
|
3
|
+
model = "gpt-5.6-terra"
|
|
4
4
|
model_reasoning_effort = "high"
|
|
5
5
|
developer_instructions = """
|
|
6
6
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
name = "test-runner-codex"
|
|
2
2
|
description = "Use to run tests, interpret failures, fix broken tests, and add regression tests for bug fixes. Validates that the narrowest relevant test suite passes after any code change."
|
|
3
|
-
model = "gpt-5.
|
|
3
|
+
model = "gpt-5.6-terra"
|
|
4
4
|
model_reasoning_effort = "low"
|
|
5
5
|
developer_instructions = """
|
|
6
6
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
name = "triage-codex"
|
|
2
2
|
description = "Assesses a CI failure diagnostic report and classifies the fix as easy or hard. Easy -> outputs a targeted fix suggestion. Hard -> signals that the investigate agent is required for root cause analysis."
|
|
3
|
-
model = "gpt-5.
|
|
3
|
+
model = "gpt-5.6-terra"
|
|
4
4
|
model_reasoning_effort = "medium"
|
|
5
5
|
developer_instructions = """
|
|
6
6
|
|
|
@@ -5,6 +5,24 @@ description: Execute an existing plan from documents/plans/ (path passed by the
|
|
|
5
5
|
|
|
6
6
|
You are the implement orchestrator. Execute a written plan phase by phase.
|
|
7
7
|
|
|
8
|
+
## Mandatory delegation contract
|
|
9
|
+
|
|
10
|
+
This skill is an orchestrator, not an implementer.
|
|
11
|
+
|
|
12
|
+
Before executing a phase:
|
|
13
|
+
|
|
14
|
+
1. Read the plan only to identify its designated agent for that phase.
|
|
15
|
+
2. Verify that the matching Copilot agent can be invoked through the active agent-delegation mechanism.
|
|
16
|
+
3. Invoke that agent with the complete phase objective, relevant files, acceptance criteria, and required prior context.
|
|
17
|
+
4. Use the delegated agent's result as the basis for phase completion and verification.
|
|
18
|
+
|
|
19
|
+
If the designated agent cannot be invoked:
|
|
20
|
+
|
|
21
|
+
- Stop immediately.
|
|
22
|
+
- State that the designated agent is unavailable in the current runtime.
|
|
23
|
+
- Do not implement, modify files, or complete the phase as a substitute.
|
|
24
|
+
- Do not silently substitute a different agent or perform the phase yourself.
|
|
25
|
+
|
|
8
26
|
## Input
|
|
9
27
|
|
|
10
28
|
The user provides a path to a plan file, e.g. `documents/plans/20260622-ui-bugs.md`. Read the plan and extract:
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: initialize
|
|
3
|
-
description: One-time environment reconciliation. First wires this tool's instruction file to the shipped MARCOS-AI-BOOTSTRAP.md rules (appending an @-include, never overwriting; creating the file if absent). Discovers applicable MCP servers and, with user approval, installs and wires them into the infra/planner agents; discovers where plan documents actually live and, after user confirmation, wires the planner/implement/docs agents to that location; scans past PRs, branch names, and commit history and, after user confirmation, customises the `
|
|
3
|
+
description: One-time environment reconciliation. First wires this tool's instruction file to the shipped MARCOS-AI-BOOTSTRAP.md rules (appending an @-include, never overwriting; creating the file if absent). Discovers applicable MCP servers and, with user approval, installs and wires them into the infra/planner agents; discovers where plan documents actually live and, after user confirmation, wires the planner/implement/docs agents to that location; scans past PRs, branch names, and commit history and, after user confirmation, customises the `pull-request` skill's convention profile; then always prompts the user to choose the model for each tier/role (pre-selecting the current model, or the closest available match when it is unavailable) and rewrites the agent files. Never commits.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
You are the initialize orchestrator. Reconcile this repo's agent network with the current environment in the phases below. This skill only edits agent and skill files, the tool's instruction entry-point, and MCP config; it never touches source code and never commits.
|
|
@@ -57,7 +57,7 @@ Role-specific override: `infra-copilot` uses `gpt-5.4`.
|
|
|
57
57
|
|
|
58
58
|
## Phase 4 — PR & contribution convention discovery
|
|
59
59
|
|
|
60
|
-
Customise the `
|
|
60
|
+
Customise the `pull-request` skill so it matches how THIS repository actually works, learned from its own history rather than assumed defaults.
|
|
61
61
|
|
|
62
62
|
1. Gather evidence of the repo's conventions:
|
|
63
63
|
- **Past PRs** — `gh pr list --state merged --limit 50 --json number,title,headRefName,body`. Infer PR-title patterns (Conventional Commits, ticket prefixes like `[ABC-123]`, sentence vs lower case), branch-name patterns (prefixes, separators, casing), and PR-body structure (required sections, checklists).
|
|
@@ -66,8 +66,8 @@ Customise the `pr` skill so it matches how THIS repository actually works, learn
|
|
|
66
66
|
- **Repo settings** — `gh repo view --json defaultBranchRef,mergeCommitAllowed,squashMergeAllowed,rebaseMergeAllowed` for the default branch and allowed merge methods.
|
|
67
67
|
2. Synthesise a concise convention profile: branch-name rules, commit-message rules, PR-title rules, PR-body/template rules, and any release-automation constraints. Prefer the dominant observed pattern; where history is sparse or inconsistent, fall back to the general Conventional Commits defaults and say so explicitly.
|
|
68
68
|
3. Present the inferred profile to the user for confirmation or edits. Do not rewrite the skill without confirmation.
|
|
69
|
-
4. On confirmation, rewrite ONLY the "Repository conventions" block of `.github/skills/
|
|
70
|
-
5. Report the resolved convention profile and confirm the `
|
|
69
|
+
4. On confirmation, rewrite ONLY the "Repository conventions" block of `.github/skills/pull-request/SKILL.md` — the text between the `<!-- CONVENTIONS:START -->` and `<!-- CONVENTIONS:END -->` markers — with the confirmed profile. Leave the rest of the skill untouched.
|
|
70
|
+
5. Report the resolved convention profile and confirm the `pull-request` skill was updated.
|
|
71
71
|
|
|
72
72
|
## Guardrails
|
|
73
73
|
- Never commit or push — you edit agent and skill files and MCP config; the user commits.
|
|
@@ -5,6 +5,23 @@ description: Formalise the two-stage planning flow. Stage 1 runs planner-discove
|
|
|
5
5
|
|
|
6
6
|
You are the planner orchestrator. Drive the two-stage planning flow.
|
|
7
7
|
|
|
8
|
+
## Mandatory delegation contract
|
|
9
|
+
|
|
10
|
+
This skill is an orchestrator, not a planner.
|
|
11
|
+
|
|
12
|
+
Before researching, asking substantive questions, or producing an outline:
|
|
13
|
+
|
|
14
|
+
1. Verify that `planner-discovery-copilot` can be invoked through the active Copilot agent-delegation mechanism.
|
|
15
|
+
2. Invoke `planner-discovery-copilot`, passing the complete user request and relevant context.
|
|
16
|
+
3. Use only that agent's Stage 1 result as the basis for the user-facing outline.
|
|
17
|
+
|
|
18
|
+
If the agent cannot be invoked:
|
|
19
|
+
|
|
20
|
+
- Stop immediately.
|
|
21
|
+
- State that `planner-discovery-copilot` is unavailable in the current runtime.
|
|
22
|
+
- Do not inspect the repository, browse, ask discovery questions, or create an outline as a substitute.
|
|
23
|
+
- Do not silently perform Stage 1 yourself.
|
|
24
|
+
|
|
8
25
|
## Stage 1 — Discovery & Outline
|
|
9
26
|
|
|
10
27
|
Invoke the `planner-discovery-copilot` agent with the user's task description and any relevant context. That agent will:
|
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
---
|
|
2
|
-
name:
|
|
2
|
+
name: pull-request
|
|
3
3
|
description: Open a pull request that follows this repository's conventions for branch names, commit messages, and PR titles and bodies. Verifies you are on a working branch, checks and repairs the branch/commits/title against the active convention profile, pushes, and opens the PR with the GitHub CLI. Never merges the PR.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
You are the
|
|
6
|
+
You are the pull-request orchestrator. Open a pull request that conforms to this repository's contribution conventions, then hand off to the user to merge. Never merge the PR yourself and never push to the default branch.
|
|
7
7
|
|
|
8
8
|
## Convention profile
|
|
9
9
|
|
|
@@ -5,6 +5,23 @@ description: Watch a GitHub Actions workflow, auto-fix failures via the agent pi
|
|
|
5
5
|
|
|
6
6
|
You are the watch-ci orchestrator. Drive the CI fix loop until the target workflow is green.
|
|
7
7
|
|
|
8
|
+
## Mandatory delegation contract
|
|
9
|
+
|
|
10
|
+
This skill is an orchestrator, not a diagnostician, triager, investigator, or implementer.
|
|
11
|
+
|
|
12
|
+
Before resolving the target, inspecting CI, or entering the fix loop:
|
|
13
|
+
|
|
14
|
+
1. Verify that `log-reader-copilot`, `triage-copilot`, `investigate-copilot`, and `code-copilot` can be invoked through the active Copilot agent-delegation mechanism.
|
|
15
|
+
2. Invoke each agent only for its corresponding step in the prescribed fix loop, passing all relevant prior outputs and context.
|
|
16
|
+
3. Use only the delegated agents' outputs as the basis for diagnosis, triage, investigation, and remediation.
|
|
17
|
+
|
|
18
|
+
If a required agent cannot be invoked:
|
|
19
|
+
|
|
20
|
+
- Stop immediately.
|
|
21
|
+
- State that the unavailable agent is unavailable in the current runtime.
|
|
22
|
+
- Do not inspect CI logs, diagnose, triage, investigate, or apply a fix as a substitute.
|
|
23
|
+
- Do not silently perform a delegated pipeline step yourself.
|
|
24
|
+
|
|
8
25
|
## Target resolution
|
|
9
26
|
|
|
10
27
|
Parse the optional input argument:
|
package/src/HUMAN.md
CHANGED
|
@@ -29,5 +29,5 @@ Once the files are written:
|
|
|
29
29
|
1. **`/planner`** — Give a basic outline of what you want to build. The agent asks clarifying questions and iterates until it has a complete plan for the feature, bugfix, or chore.
|
|
30
30
|
2. **`/clear`** — Clear the context window.
|
|
31
31
|
3. **`/implement`** — Paste the path to the plan that was created, e.g. `documents/plans/20260101-plan.md`.
|
|
32
|
-
4. **`/
|
|
32
|
+
4. **`/pull-request`** — Open a pull request with Conventional Commit messages so the release-please workflow can cut a release once merged.
|
|
33
33
|
5. **`/watch-ci`** — Paste the PR or GitHub Actions run. It watches the build to make sure everything passes, fixing bugs in real time if needed.
|
|
@@ -139,11 +139,11 @@ cannot edit locally, so it watches, diagnoses, and reports the fix back to the u
|
|
|
139
139
|
**Guardrails:** Never commits or pushes — agents edit files, the user commits. Never works on `main` (uses the plan's branch). Honours each phase's agent designation exactly; stops on a failed phase.
|
|
140
140
|
|
|
141
141
|
### initialize
|
|
142
|
-
**Purpose:** One-time environment reconciliation. First ensures the tool's instruction file (`CLAUDE.md`, `AGENTS.md`, or `.github/copilot-instructions.md`) references the shipped `MARCOS-AI-BOOTSTRAP.md` rules — appending a short `@MARCOS-AI-BOOTSTRAP.md` include (never overwriting existing content), or creating the file if it does not exist. Discovers applicable MCP servers (via the MCP Servers discovery → policy-check → install flow) and, with user approval, installs and wires them into the `infra` and `planner` agents. Discovers where plan documents actually live in the repo and, after explicit user confirmation, wires the `planner`, `implement`, and `docs` agents/skills to that location. Scans the repository's history (past merged PRs, branch names, commit subjects, and any CONTRIBUTING / PR-template / commit-lint / release-automation config) and, after user confirmation, customises the `
|
|
143
|
-
**Pipeline:** rules-file include wiring → MCP discovery → user approval → install + wire agents → plans-location discovery → user confirmation → rewrite plan-location references → PR/commit-convention discovery → user confirmation → customise the `
|
|
144
|
-
**Guardrails:** Never commits or pushes. Only edits agent/skill files, the tool's instruction entry-point, and MCP config — never source code. Appends to (never clobbers) an existing instruction file. Never installs a policy-blocked or unapproved server. Never changes the plans location or `
|
|
142
|
+
**Purpose:** One-time environment reconciliation. First ensures the tool's instruction file (`CLAUDE.md`, `AGENTS.md`, or `.github/copilot-instructions.md`) references the shipped `MARCOS-AI-BOOTSTRAP.md` rules — appending a short `@MARCOS-AI-BOOTSTRAP.md` include (never overwriting existing content), or creating the file if it does not exist. Discovers applicable MCP servers (via the MCP Servers discovery → policy-check → install flow) and, with user approval, installs and wires them into the `infra` and `planner` agents. Discovers where plan documents actually live in the repo and, after explicit user confirmation, wires the `planner`, `implement`, and `docs` agents/skills to that location. Scans the repository's history (past merged PRs, branch names, commit subjects, and any CONTRIBUTING / PR-template / commit-lint / release-automation config) and, after user confirmation, customises the `pull-request` skill's convention profile to match. Then always prompts the user, via a dropdown, to choose the model for each tier/role — pre-selecting the currently configured model when it is available, or the closest available match when it is not — and rewrites the agent files.
|
|
143
|
+
**Pipeline:** rules-file include wiring → MCP discovery → user approval → install + wire agents → plans-location discovery → user confirmation → rewrite plan-location references → PR/commit-convention discovery → user confirmation → customise the `pull-request` skill → enumerate available models → user chooses model per tier/role (always) → rewrite agent files.
|
|
144
|
+
**Guardrails:** Never commits or pushes. Only edits agent/skill files, the tool's instruction entry-point, and MCP config — never source code. Appends to (never clobbers) an existing instruction file. Never installs a policy-blocked or unapproved server. Never changes the plans location or `pull-request` conventions without explicit user confirmation. Idempotent for include wiring, MCP wiring, and the plans location; model selection is always offered, but keeping the current choice leaves files unchanged.
|
|
145
145
|
|
|
146
|
-
###
|
|
146
|
+
### pull-request
|
|
147
147
|
**Purpose:** Open a pull request that follows THIS repository's contribution conventions — branch names, commit-message format, PR title, and PR body — defaulting to widely-used best practices (kebab-case typed branches, Conventional Commits) until the `initialize` skill customises the convention profile from the repo's own history. Prevents malformed PRs and, where release automation (e.g. release-please) is in use, the failure mode where a non-conventional commit lands on the default branch and the release is silently skipped.
|
|
148
148
|
**Pipeline:** resolve the default branch → branch check (never the default branch) → validate/repair the branch name and commit subjects against the active convention → push → derive and validate a conventional PR title and body → `gh pr create` → report the PR URL and any repo-specific merge/release guidance.
|
|
149
149
|
**Guardrails:** Never merges the PR — opening it is the final step; the user merges. Never pushes to or commits on the default branch. Force-pushes only to complete a reword/rebase the user explicitly approved. Never uses `--no-verify`.
|