菜单
Commit, push, and create a merge request (GitLab) or pull request (GitHub) for documentation changes. Creates a feature branch if the repo is on main/master. Replaces docs-workflow-prepare-branch, docs-workflow-commit, and docs-workflow-create-mr.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | docs-workflow-create-merge-request |
| description | Commit, push, and create a merge request (GitLab) or pull request (GitHub) for documentation changes. Creates a feature branch if the repo is on main/master. Replaces docs-workflow-prepare-branch, docs-workflow-commit, and docs-workflow-create-mr. |
| model | claude-haiku-4-5@20251001 |
| argument-hint | <ticket> --base-path <path> [--draft] [--repo-path <path>] |
| allowed-tools | Bash, Read |
Step skill for the docs-orchestrator pipeline. After writing and reviews are complete, this step creates a feature branch (if needed), commits the manifest-listed files, pushes to the remote, and creates an MR/PR via gh (GitHub) or glab (GitLab).
Skipped in draft mode (--draft flag). When --repo-path is set, the script operates in the target repo but expects the user to have already switched to a feature branch.
$1 — JIRA ticket ID (required)--base-path <path> — Base output path (e.g., .agent_workspace/proj-123)--draft — If present, skip all git operations--repo-path <path> — Target documentation repository (must already be on a feature branch)<base-path>/writing/step-result.json
Contains the files array of absolute paths to commit (written by the writing step).
<base-path>/create-merge-request/step-result.json
Combined sidecar with commit, push, and MR/PR metadata.
Run the script, passing through all arguments:
bash ${CLAUDE_SKILL_DIR}/scripts/create_merge_request.sh <ticket> --base-path <base-path> [--draft] [--repo-path <path>]
The script handles:
--draft is setmain or master (and no --repo-path), creates <ticket-lowercase> branch from HEAD or switches to it if it already existsmain/master with --repo-path (externally managed repos must be on a feature branch)writing/step-result.json and filters to files under the repo rootdocs(<ticket>): add generated documentation--force-with-lease to originrequirements/step-result.json title field or first heading in requirements.mdgh pr create (GitHub) or glab mr create (GitLab), with fork detection for GitLab via the upstream remotestep-result.json with commit_sha, branch, pushed, url, action, platform, skipped, and skip_reason fieldsCheck that all environment variables and CLI tools required by the docs-skills plugin are available. Use when setting up a new environment, troubleshooting missing prerequisites, or before running a workflow for the first time.
Read and analyze JIRA issues from Red Hat Issue Tracker. Use this skill to fetch issue details, search issues, extract comments and discussions, categorize issues (bugs, CVEs, features, stories), analyze custom fields (release notes, fix versions), retrieve Git links, traverse ticket graphs (parent, children, siblings, links), and generate summaries. This skill is read-only and cannot modify JIRA issues. Requires jira and ratelimit Python packages.
Documentation workflow orchestrator. Reads the step list from .agent_workspace/docs-workflow.yaml (or the plugin default). Runs steps sequentially, manages progress state, handles iteration and confirmation gates. Claude is the orchestrator — the YAML is a step list, not a workflow engine.
Write documentation from a documentation plan. Dispatches the docs-writer agent. Supports AsciiDoc (default) and MkDocs formats. Default placement is UPDATE-IN-PLACE; use --draft for staging area. Also supports fix mode for applying technical review corrections.
Score documentation quality and intent alignment using LLM judge agents (Opus). Dispatches two judge agents in parallel (doc_quality, intent_alignment), extracts specific gaps from AC coverage analysis, and cross-references against scope-req-audit evidence. Produces pass/fail gate with actionable gap list. Iteration logic is owned by the orchestrator, not this skill.
Run code-learner analysis on a source repository for the docs orchestrator workflow. Dispatches a subagent to run learn-code, keeping the heavy orchestration out of the main context. Produces ONBOARDING.md, module registry, per-module summaries, and cross-module relationship data.