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

analyze-codebase-bugs

Run a structured bug-focused code review for selected files, folders, or the whole workspace.

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

설치 방법 보기

포함된 파일(1)

  • SKILL.md1.7 KB

SKILL.md(원문)

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

Analyze the codebase for real defects and regression risks.

Input:

  • Treat the skill argument as scope (for example: a feature folder, changed files, or a specific flow).
  • If no scope is provided, analyze the most relevant production code paths in the workspace.

Primary objective:

  • Find concrete bugs, broken behavior, risky assumptions, and missing tests.
  • Prioritize findings by severity.
  • Avoid style-only feedback unless it causes runtime, data, security, accessibility, or maintenance risk.

Required workflow:

  1. Gather context with targeted code search and file reads.
  2. Validate behavior assumptions from code, tests, and configuration.
  3. Report findings first, ordered by severity.
  4. For each finding include:
    • Severity: Critical, High, Medium, or Low
    • Location: exact file path and line link
    • Impact: what breaks and when
    • Evidence: code-level reason
    • Fix suggestion: minimal, safe change
    • Test gap: what test should exist or be updated
  5. After findings, include:
    • Open questions and assumptions
    • Brief change summary only if no critical blockers exist

Output format:

  • Start with section: Findings
  • If there are no findings, state explicitly: No functional bugs found.
  • Then list residual risks and test coverage gaps.
  • Keep the response concise, specific, and actionable.

Quality bar:

  • Do not invent issues without evidence.
  • Do not request broad refactors unless directly needed to fix a defect.
  • Prefer deterministic reproduction hints when possible.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling.

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

danielsogl/copilot-workflow-demo392026년 10월 22일 업데이트

Generate an Angular Signal Forms component with schema validation and dynamic field management for a given entity.

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

danielsogl/copilot-workflow-demo392026년 10월 22일 업데이트

bdd

무료

Write disciplined Behavior-Driven Development specs and tests with Gherkin / Cucumber. Use whenever the user mentions BDD, Gherkin, Cucumber, .feature files, Given/When/Then, scenarios, Scenario Outline, Background, step definitions, acceptance criteria, executable specifications, living documentation, the Three Amigos, or Example Mapping. Also trigger when the user asks to "write tests in plain English", convert acceptance criteria into tests, design step definitions, refactor an imperative or UI-coupled feature file, or wire up BDD with Vitest (unit/component) or Playwright (end-to-end). Do NOT use for pure unit tests with no business-readable contract, pure performance/load tests, or generic test-framework questions unrelated to behavior specs.

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

danielsogl/copilot-workflow-demo392026년 10월 22일 업데이트

Build, refactor, and architect Angular state with the @ngrx/signals Signal Store. Use whenever the user mentions signalStore, withState, withMethods, withComputed, withHooks, withLinkedState, withFeature, signalStoreFeature, withEntities, rxMethod, signalMethod, patchState, the SignalStore events plugin (withReducer, withEventHandlers), or wants to refactor BehaviorSubject/service-based state to Signal Store. Also use for designing custom store features, request status, optimistic updates, entity collections, and the store/service split in Angular. Do NOT use for @ngrx/store (classic Redux), createReducer/createEffect, or generic RxJS questions unrelated to Signal Store.

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

danielsogl/copilot-workflow-demo392026년 10월 22일 업데이트

Generate an NgRx Signal Store with complete CRUD operations (API service, store, tests) for a given entity.

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

danielsogl/copilot-workflow-demo392026년 10월 22일 업데이트

Review the current branch against its base branch: lint, tests, architecture and Angular 22 conventions, reported by severity.

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

danielsogl/copilot-workflow-demo392026년 10월 22일 업데이트

danielsogl의 스킬 모두 보기

이 스킬의 문제 신고