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
Maintain developer-facing documentation for Build with WordPress.
78
-
79
-
Manual dispatch runs the bootstrap flow and should create or improve the initial developer documentation structure if the repository does not already have one. Push-triggered merge checks run the maintenance flow and should make the smallest source-grounded documentation update needed for newly merged code or finish with no changes when documentation is current.
80
-
81
-
Write the developer documentation as repository docs: `docs/README.md` as the index, focused topic pages under `docs/**`, and `plugins/**/README.md` only when a plugin package needs local developer-facing contract notes. For the bootstrap surface, prefer `docs/architecture.md`, `docs/generated-outputs.md`, `docs/skills-and-integrations.md`, and `docs/contributor-workflows.md` as the main topic pages.
82
-
83
-
Cover the repository purpose, package layout, generated plugin artifacts, build and verification commands, skill packaging, Studio integration points, and contributor workflows. Document agent/plugin configuration files and generated plugin artifacts from those repository docs and plugin README files. Use the read-only context aliases `studio` and `wordpress-agent-skills` only as source evidence for integration behavior.
84
-
85
-
Write the documentation files into the runner-provided workspace and leave publication to the runner; it commits the workspace changes and opens the documentation pull request.
"pr_title_template": "docs: maintain Build with WordPress developer documentation",
145
-
"pr_body_template": "## Build with WordPress developer docs\n\nThe technical-docs-agent Data Machine agent (Automattic/docs-agent `bundles/technical-docs-agent`) updated developer-facing documentation in this repository.\n\n- Flow: {task_id}\n- Publication opened by the runtime-agent-full-run runner.\n",
Maintain developer-facing documentation for Build with WordPress.
105
+
106
+
Manual dispatch runs the bootstrap flow and should create or improve the initial developer documentation structure if the repository does not already have one. Push-triggered merge checks run the maintenance flow and should make the smallest source-grounded documentation update needed for newly merged code or finish with no changes when documentation is current.
107
+
108
+
Write the developer documentation as repository docs: `docs/README.md` as the index, focused topic pages under `docs/**`, and `plugins/**/README.md` only when a plugin package needs local developer-facing contract notes. For the bootstrap surface, prefer `docs/architecture.md`, `docs/generated-outputs.md`, `docs/skills-and-integrations.md`, and `docs/contributor-workflows.md` as the main topic pages.
109
+
110
+
Cover the repository purpose, package layout, generated plugin artifacts, build and verification commands, skill packaging, Studio integration points, and contributor workflows. Document agent/plugin configuration files and generated plugin artifacts from those repository docs and plugin README files. Use the read-only context aliases `studio` and `wordpress-agent-skills` only as source evidence for integration behavior.
Maintain live agent skill instructions and generated packaged skill outputs for Build with WordPress.
77
-
78
-
Run the skills maintenance flow and make the smallest source-grounded skill update needed for newly merged code, or finish with no changes when the skills are current. Edit live skill instructions under `skills/**`, packaged skill outputs under `plugins/**/skills/**`, and `plugins/**/README.md` only when a plugin package needs local developer-facing contract notes.
79
-
80
-
Use the read-only context aliases `studio` and `wordpress-agent-skills` only as source evidence for integration and packaging behavior.
81
-
82
-
Write the skill changes into the runner-provided workspace and leave publication to the runner; it commits the workspace changes and opens the skills pull request.
"pr_title_template": "docs: maintain Build with WordPress live skills",
140
-
"pr_body_template": "## Build with WordPress live skills\n\nThe skills-agent Data Machine agent (Automattic/docs-agent `bundles/skills-agent`) updated live skill instructions and generated packaged skill outputs in this repository.\n\n- Flow: {task_id}\n- Publication opened by the runtime-agent-full-run runner.\n",
141
-
"commit_message_template": "docs: maintain live skills"
142
-
}
143
-
success_requires_pr: false
144
-
# Public deps + same-repo target → default GITHUB_TOKEN suffices; no
145
-
# Homeboy GitHub App token required (runner falls back to GITHUB_TOKEN).
0 commit comments