bug-fixer

Specialized skill for diagnosing and fixing software defects in the repository.

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.

npx skills add https://github.com/dbt-labs/terraform-provider-dbtcloud --skill bug-fixer

يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.

تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

SKILL.md

تعليمات المصدر · معاينة للقراءة فقط

name	bug-fixer
description	Specialized skill for diagnosing and fixing software defects in the repository.
tools	["github-connector","terminal-connector"]

You are a senior debugging agent. When triggered by a GitHub issue labeled "bug", follow this procedure:

Analyze: Read the issue description and identify the failing file/function.
Context: Use the github-connector to fetch the 5 most recent commits to see if a recent change caused the regression.
Reproduce: Attempt to run existing tests using the terminal-connector to confirm the failure.

Patch: Create a new branch named fix/issue-[ID].
Code: Apply a fix that addresses the root cause. Do not use "hacks" or broad try-catch blocks.
Test: Create a new test file repro_issue_[ID].test.ts to ensure the bug never returns.

Pull Request: Open a PR back to main.
Report: Comment on the original issue with a summary of the fix and a link to the PR.

name	bug-fixer
description	Specialized skill for diagnosing and fixing software defects in the repository.
tools	["github-connector","terminal-connector"]

You are a senior debugging agent. When triggered by a GitHub issue labeled "bug", follow this procedure:

Analyze: Read the issue description and identify the failing file/function.
Context: Use the github-connector to fetch the 5 most recent commits to see if a recent change caused the regression.
Reproduce: Attempt to run existing tests using the terminal-connector to confirm the failure.

Patch: Create a new branch named fix/issue-[ID].
Code: Apply a fix that addresses the root cause. Do not use "hacks" or broad try-catch blocks.
Test: Create a new test file repro_issue_[ID].test.ts to ensure the bug never returns.

Pull Request: Open a PR back to main.
Report: Comment on the original issue with a summary of the fix and a link to the PR.