메뉴
Check 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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
Classify JIRA requirements by code evidence status before planning. Uses learn-code analysis data and source code inspection to determine if each requirement is grounded, partial, or absent. Fans out one subagent per requirement for isolated classification. Prevents hallucinated documentation for unimplemented features and surfaces gaps for implemented ones. Conditional on has_source_repo.
| name | validate-plugin-prereqs |
| description | Check 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. |
Run the prerequisite checker:
bash ${CLAUDE_SKILL_DIR}/scripts/validate_prereqs.sh
The script loads ~/.env and ./.env, then checks all required and optional environment variables and CLI tools. It prints a human-readable table and exits with code 0 (all required items present) or 1 (something missing).
If any required items are missing, tell the user what's needed and how to fix it:
JIRA_API_TOKEN / JIRA_EMAIL: Add to ~/.env or .env. Required for JIRA-related skills (jira-reader, jira-writer, create-jira, jira-ready).GITHUB_TOKEN: Add to ~/.env or .env. Needed for GitHub-based skills (git-pr-reader, understand-pull-request).GITLAB_TOKEN: Add to ~/.env or .env. Needed only for GitLab-based repositories.python3: Install Python 3.10+.uv: Install with curl -LsSf https://astral.sh/uv/install.sh | sh.git: Install via system package manager.jq: Install via system package manager.gh: Install from https://cli.github.com/.glab: Install from https://gitlab.com/gitlab-org/cli. Required for GitLab workflows (create-merge-request, git-pr-reader).vale: Install from https://vale.sh/docs/install/. Optional — only needed for style review skills.shellcheck / ruff: Optional dev/CI tools.