원클릭으로 Manus에서 모든 스킬 실행

fix-issues

스타1

포크0

업데이트2026년 7월 16일 21:01

Validate reported issues against the codebase and fix confirmed ones with minimal, safe changes. Use when the user provides a list of issues, bugs, or review findings to triage and fix.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Kestral-Team

Kestral-Team/kstack

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Fix Issues

Discuss each issue, validate whether it is real, then fix all real issues with minimal changes.

Workflow

Restate each reported issue and mark one of:
- Confirmed (real bug/risk)
- Not reproducible (explain why)
- Needs clarification (missing facts)
For confirmed issues, identify the smallest safe fix and apply changes sequentially.
After each fix, re-evaluate whether later planned fixes still make sense.
Run lint/typecheck on touched files.
Summarize:
- what was fixed
- what was rejected (and why)
- remaining risks or follow-ups

Required Validation Checks

Transaction scope: no network/LLM/GCS I/O inside long DB transactions unless intentional and justified.
Rollback ownership (TOCTOU guard): destructive cleanup must use authoritative write-path ownership signals (for example wasCreated), never stale pre-check state.
Atomicity: related writes that must commit together share the same transaction client.
Error masking: cleanup failures should be logged and should not hide the original business failure.

Project Context

Read context.md and apply it as additional project-specific constraints layered on top of this workflow. If it does not exist, skip this section.

이 저장소의 다른 Skills

같은 저장소

acceptance-check

Kestral-Team/kstack

Validate the branch diff against the task's acceptance criteria before marking it done. Use when implementation looks complete, before a status update to done/awaiting_review, or when the user asks "did we cover everything?"

2026-07-161

babysit-pr

Kestral-Team/kstack

Get a PR to merge-ready state by triaging comments, resolving conflicts, and fixing CI. Includes Graphite detection, migration conflict handling, and conflict resolution. Use when the user asks to babysit a PR, get a PR merge-ready, or fix CI on a PR.

2026-07-161

cleanup-plans

Kestral-Team/kstack

Audit implementation plans for the current user, verify status against the codebase, and archive completed plans. Use when the user asks to clean up plans, audit plan status, or archive completed plans.

2026-07-161

code-review

Kestral-Team/kstack

One-pass AI code review of a PR or branch diff (tech-lead style). Use when the user asks for a code review, PR review, AI review, or wants code quality, architecture, bugs, and patterns reviewed.

2026-07-161

code-simplify

Kestral-Team/kstack

Simplify changed code in a PR or branch for readability while preserving behavior. Use when the user asks to simplify code, reduce complexity, clean up a PR, or improve readability of recent changes.

2026-07-161

context-evolve

Kestral-Team/kstack

Capture new project-specific learnings into context files. Runs during reviews or after debugging to evolve the project's skill knowledge base. Use when the thread reveals patterns, anti-patterns, conventions, or codebase gotchas that should be remembered.

2026-07-161

name	fix-issues
kstack	true
description	Validate reported issues against the codebase and fix confirmed ones with minimal, safe changes. Use when the user provides a list of issues, bugs, or review findings to triage and fix.

Fix Issues

Discuss each issue, validate whether it is real, then fix all real issues with minimal changes.

Workflow

Restate each reported issue and mark one of:
- Confirmed (real bug/risk)
- Not reproducible (explain why)
- Needs clarification (missing facts)
For confirmed issues, identify the smallest safe fix and apply changes sequentially.
After each fix, re-evaluate whether later planned fixes still make sense.
Run lint/typecheck on touched files.
Summarize:
- what was fixed
- what was rejected (and why)
- remaining risks or follow-ups

Required Validation Checks

Transaction scope: no network/LLM/GCS I/O inside long DB transactions unless intentional and justified.
Rollback ownership (TOCTOU guard): destructive cleanup must use authoritative write-path ownership signals (for example wasCreated), never stale pre-check state.
Atomicity: related writes that must commit together share the same transaction client.
Error masking: cleanup failures should be logged and should not hide the original business failure.

Project Context

Read context.md and apply it as additional project-specific constraints layered on top of this workflow. If it does not exist, skip this section.