본문으로 건너뛰기
cccskills
무료GitHub에 공개

archify-review

Review Archify issues, pull requests, and code by weighing user value, implementation and maintenance costs, and wider impact. Use evidence to decide whether work is worthwhile, compare alternatives, and identify questions that still affect the decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Review Archify issues, PRs, or code through value, cost, and impact to support evidence-based maintenance decisions. Use for issue triage, change reviews, and code quality assessments.

tt-a1i/archify
설치 방법 보기

이럴 때 유용합니다

  • Prioritizing reported issues
  • Reviewing the cost and impact of a pull request
  • Assessing code maintainability
  • Comparing alternative solutions to a problem

포함된 파일(1)

  • SKILL.md1.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Archify Review

Judge whether a problem is worth addressing and an approach is worth maintaining over time.

  • Value: Identify the real problem, who benefits, how often it occurs, its consequences, and whether it is worth addressing now.
  • Cost: Consider implementation and verification effort, along with the future cost of understanding, changing, and maintaining the code. Prefer existing capabilities and keep the solution proportional to the problem.
  • Impact: Identify affected behavior and modules, consequences for users and future development, and whether the change improves maintainability or adds coupling and constraints.

Consider maintainability, complexity, compatibility, performance, and other relevant concerns within these three dimensions, according to the specific problem.

Ground judgments in evidence: verify the target revision and relevant facts, distinguish direct verification from existing evidence and assumptions, and choose checks that resolve the key uncertainties.

Explain whether the work is worthwhile, the approach's cost and impact, any better alternatives, and unresolved questions that matter to the decision. Give reasons and scale the detail to the importance of each concern.

For repository-specific review and contribution requirements, consult REVIEWING.md and CONTRIBUTING.md as needed.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

archify

무료

Turn plain-language descriptions, Mermaid diagrams, or repository evidence into interactive standalone HTML diagrams. Create system maps, workflows, timelines, database relationships, and everyday process diagrams, with automated validation, light and dark themes, and image, SVG, or WebM export.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Mapping a system from repository evidence
  • Explaining approval steps or travel plans
  • Visualizing database tables and relationships
tt-a1i/archify8.6만2026년 10월 19일 업데이트

archify-tuning

무료

Evaluate improvements to Archify diagrams using actual outputs and agent work records. Compare accuracy, readability, and total delivery time to investigate layout, connection routing, diagnostics, and authoring guidance, then document what the evidence supports.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Comparing diagram layouts and connection routes
  • Investigating repeated diagram repair attempts
  • Testing changes to authoring guidance
tt-a1i/archify8.6만2026년 10월 19일 업데이트

simplify-codebase

무료

Audit a codebase for unnecessary complexity, including dead code, duplicated state, redundant interfaces, and obsolete compatibility paths. Receive evidence-backed simplification candidates, or authorize changes that remove justified targets and validate the behavior that must remain.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Finding code that can be safely removed
  • Consolidating duplicated state or APIs
  • Reviewing obsolete compatibility paths and design records
tt-a1i/archify8.6만2026년 10월 19일 업데이트

test-value

무료

Evaluate slow, unreliable, duplicated, or brittle tests by the behavior they protect and their maintenance cost. Use it to choose focused checks, justify additions or removals, and distinguish product bugs from outdated expectations or environment failures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing slow or unreliable tests
  • Choosing tests for a code change
  • Reviewing test changes before a commit or PR
tt-a1i/archify8.6만2026년 10월 19일 업데이트

tt-a1i의 스킬 모두 보기

이 스킬의 문제 신고