ワンクリックでManusで任意のスキルを実行

fix

スター4

フォーク1

更新日2026年3月10日 10:03

Systematic approach to fixing bugs and issues in code. Use when asked to "fix this bug", "debug this issue", "resolve this error", or when troubleshooting code problems. Provides structured debugging and resolution workflow.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

b1mango

b1mango/Agent-Skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Fix

Systematic approach to diagnosing and fixing code issues.

When to Use

User reports a bug or error
User asks to "fix this", "debug this", or "resolve this error"
Troubleshooting failing tests
Resolving build or runtime errors

Fix Workflow

1. Understand the Problem

What is the expected behavior?
What is the actual behavior?
When did it start happening?
Can it be reproduced consistently?
What error messages or logs are available?

2. Reproduce

Identify minimal reproduction steps
Confirm the issue exists in the current codebase
Check if the issue is environment-specific

3. Diagnose

Read error messages and stack traces carefully
Identify the root cause vs symptoms
Check recent changes (git log, git diff)
Add targeted logging if needed
Use debugger breakpoints for complex issues

4. Fix

Make the minimal change that fixes the root cause
Don't fix symptoms; fix the underlying issue
Consider edge cases the fix might affect
Maintain backward compatibility when possible

5. Verify

Confirm the original issue is resolved
Run existing tests to check for regressions
Add a test case that would have caught this bug
Test edge cases related to the fix

6. Document

Add a brief comment explaining non-obvious fixes
Update relevant documentation if behavior changed
Note the fix in commit message with issue reference

Common Bug Patterns

Pattern	Signs	Typical Fix
Null reference	`Cannot read property of undefined`	Add null checks, optional chaining
Race condition	Intermittent failures	Use proper async/await, locks
State mutation	Unexpected state changes	Use immutable updates
Stale closure	Old values in callbacks	Use refs or functional updates
Memory leak	Growing memory usage	Clean up subscriptions, listeners
Off-by-one	Wrong array indices	Check loop bounds

このリポジトリの他の Skills

同じリポジトリ

code-review-skill

b1mango/Agent-Skills

Compatibility alias for the canonical code-reviewer skill. Use only when older prompts or users explicitly reference code-review-skill; otherwise prefer Agent-Skills/code-reviewer/SKILL.md for code reviews, PR reviews, diffs, staged or unstaged changes, and systematic analysis of correctness, security, performance, maintainability, and tests.

2026-04-264

code-reviewer

b1mango/Agent-Skills

Professional code review workflow for local changes, pull requests, diffs, or pasted code. Use when asked to review code, check PRs, inspect staged or unstaged changes, assess correctness, security, performance, maintainability, tests, or produce actionable findings with severity and file or line references.

2026-04-264

web-access

b1mango/Agent-Skills

所有联网操作必须通过此 skill 处理，包括：搜索、网页抓取、登录后操作、网络交互等。触发场景：用户要求搜索信息、查看网页内容、访问需要登录的网站、操作网页界面、抓取社交媒体内容（小红书、微博、推特等）、读取动态渲染页面、以及任何需要真实浏览器环境的网络任务。

2026-03-254

scrapling

b1mango/Agent-Skills

使用 Scrapling 进行高级网页抓取，支持反爬绕过（Cloudflare Turnstile）、隐身浏览、自适应解析、Spider 爬虫框架。适用于被反爬保护的网站、动态内容抓取、批量数据提取等场景。

2026-03-244

geopolitical-deep-analysis

b1mango/Agent-Skills

中文时政地缘政治深度分析写作技能。用于撰写去AI味的、具有杂志长文风格的深度时政分析文章。涵盖去AI化规则、长段叙述规范、分析推理要求和数据引用标准。适用于中东局势、大国博弈、战争分析、国际关系等题材。

2026-03-124

codegen-diagram

b1mango/Agent-Skills

Generate code architecture diagrams from source code. Use when asked to "generate a diagram", "visualize code architecture", "create a class diagram", "draw a sequence diagram", or when converting code into visual Mermaid/PlantUML diagrams.

2026-03-104

Fix

Systematic approach to diagnosing and fixing code issues.

When to Use

User reports a bug or error

User asks to "fix this", "debug this", or "resolve this error"

Troubleshooting failing tests

Resolving build or runtime errors

Fix Workflow

1. Understand the Problem

What is the expected behavior?

What is the actual behavior?

When did it start happening?

Can it be reproduced consistently?

What error messages or logs are available?

2. Reproduce

Identify minimal reproduction steps

Confirm the issue exists in the current codebase

Check if the issue is environment-specific

3. Diagnose

Read error messages and stack traces carefully

Identify the root cause vs symptoms

Check recent changes (git log, git diff)

Add targeted logging if needed

Use debugger breakpoints for complex issues

4. Fix

Make the minimal change that fixes the root cause

Don't fix symptoms; fix the underlying issue

Consider edge cases the fix might affect

Maintain backward compatibility when possible

5. Verify

Confirm the original issue is resolved

Run existing tests to check for regressions

Add a test case that would have caught this bug

Test edge cases related to the fix

6. Document

Add a brief comment explaining non-obvious fixes

Update relevant documentation if behavior changed

Note the fix in commit message with issue reference

Common Bug Patterns

Pattern

Signs

Typical Fix

Null reference

Cannot read property of undefined

Add null checks, optional chaining

Race condition

Intermittent failures

Use proper async/await, locks

State mutation

Unexpected state changes

Use immutable updates

Stale closure

Old values in callbacks

Use refs or functional updates

Memory leak

Growing memory usage

Clean up subscriptions, listeners

Off-by-one

Wrong array indices

Check loop bounds

name	fix
description	Systematic approach to fixing bugs and issues in code. Use when asked to "fix this bug", "debug this issue", "resolve this error", or when troubleshooting code problems. Provides structured debugging and resolution workflow.