القائمة
Write implementation-ready GitHub issues, engineering-report PR bodies, and current-head revision comments without importing repo-specific policy.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Ralph build workflow for Kapi. Use when /kapi-ralph is active or when implementing from a prepared Ralph workspace with AGENTS.md, IMPLEMENTATION_PLAN.md, specs, shared state.json, handoff.json, verify.md, one-task iterations, validation backpressure, and reviewer closeout.
Ralph planning workflow for Kapi. Use when a Ralph workspace needs interview-driven planning, specs, AGENTS.md, IMPLEMENTATION_PLAN.md, state.json, handoff.json, and critic/architect consensus before /kapi-ralph execution.
Use when an active Kapi workflow is in context or the user explicitly asks for /kapi-* workflow structure. Preserve thin-by-default behavior and follow the active workflow contract, artifacts, evidence, and worker guidance.
Repo-local guidance for isolated Ilchul review runners that produce structured, low-noise findings.
Kapi-bundled Deep Interview guidance for main-agent, artifact-backed requirements discovery before Ralph or Autoresearch handoff.
| name | issue-pr-revision-authoring |
| description | Write implementation-ready GitHub issues, engineering-report PR bodies, and current-head revision comments without importing repo-specific policy. |
| version | 1.0.0 |
| license | MIT |
| metadata | {"tags":["github","issue-authoring","pull-requests","revision-comments","engineering-reports"]} |
Use this skill when drafting or revising GitHub issues, pull request bodies, or review-response comments. The goal is execution-design authoring: enough concrete contract, evidence, and verification detail for an implementer or reviewer to proceed without a separate meeting.
This skill standardizes writing quality only; it does not define branch protection, reviewer bots, merge gates, deployment policy, webhook behavior, or profile authority semantics.
Use the smallest section set that makes the work executable and reviewable. Add paths, commands, examples, acceptance criteria, and evidence whenever they prevent ambiguity.
Use when implementation should be possible directly from the issue. Include: summary/motivation, observed problem, proposed solution, CLI/API/UX examples, likely files or surfaces, dependencies/configuration, security/performance/compatibility considerations, non-goals, acceptance criteria, and verification plan.
Use when work is partially implemented and the issue tracks remaining gaps. Include: current status summary, feature/surface table, completed vs remaining work, architecture or surface map, acceptance criteria with status, and available evidence.
Use for performance, correctness, production behavior, or uncertain root cause work where implementation should not start from guesses. Include: environment, measurements/reproduction evidence, observations separated from hypotheses, suggested investigations, reproduction commands, and related issues/PRs/docs.
A PR body is an engineering report, not a changelog. Explain final behavior, linked issue/close intent, problem and defect split, changes by file/surface, design decisions and rejected alternatives, tests, exact verification commands, acceptance status, and remaining risks or follow-up. Use templates/pr-body.md; use Refs #N instead of Closes #N for partial work.
A revision comment should be current-head, feedback-addressing, and evidence-bearing. Do not merely say “fixed.” Include current head SHA, intent, findings addressed, changed files/surfaces, tests/verification, docs/release-note impact, remaining items, and ready-for-review statement. If a repository requires a review trigger phrase, follow that repository's workflow; do not bake a specific bot name or trigger phrase into this generic template.
Keep these layers out unless a downstream repo adds them in its own workflow docs:
templates/issue.md — execution-design, current-state tracker, and evidence-driven investigation issue sections.templates/pr-body.md — engineering-report PR body sections.templates/revision-comment.md — current-head review-response/finalization comment.