Skip to content
cccskills
FreePublished on GitHub

analyze-codebase-bugs

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

The English summary is being prepared. Showing the original description.

danielsogl/copilot-workflow-demo
See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

angular-developer

Free

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.

The English summary is being prepared. Showing the original description.

danielsogl/copilot-workflow-demo39Updated Oct 22, 2026

angular-signal-forms

Free

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

The English summary is being prepared. Showing the original description.

danielsogl/copilot-workflow-demo39Updated Oct 22, 2026

bdd

Free

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.

The English summary is being prepared. Showing the original description.

danielsogl/copilot-workflow-demo39Updated Oct 22, 2026

ngrx-signals

Free

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.

The English summary is being prepared. Showing the original description.

danielsogl/copilot-workflow-demo39Updated Oct 22, 2026

ngrx-signals-store-crud

Free

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

The English summary is being prepared. Showing the original description.

danielsogl/copilot-workflow-demo39Updated Oct 22, 2026

review-branch

Free

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

The English summary is being prepared. Showing the original description.

danielsogl/copilot-workflow-demo39Updated Oct 22, 2026

See all skills by danielsogl

Report a problem with this skill