Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free
  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Voice Mode
  • Voice HUD
  • Web Search
  • Image Generation
  • Video Generation
  • Audio Generation
  • Transcription
  • Drive
  • Credentials
  • Sharing
  • Workspaces
  • Tasks
  • Memory
  • Agents
  • Subagents
  • Automations
  • Skills
  • idapt Code
  • Code Execution
  • Computers
  • Computer Use
  • Computer Assist · Soon
  • Containers
  • Cloud Computers
  • Local AI
  • AI Gateway
  • API & SDK
  • CLI
  • MCP
  • Tunnels
  • All features →
  • LLM cost calculator
  • Token counter
  • Context window checker
  • Can I run it
  • Model picker quiz
  • Savings finder
  • Video cost estimator
  • Text to speech cost
  • Transcription cost
  • API endpoint tester
  • All free tools →
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Skills
  • Learn
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • idapt Code
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)
All skills
Code

Fix a GitHub issue

Take an issue from its description to a reviewed change.

Fill it in

The issue to work.

Where to make the change.

How you want the work handed back.

Your prompt

Work [your issue url] in [your repository].

Read the issue and its comments before touching anything. Half of what looks
like the problem in the title turns out to be a symptom somebody already
diagnosed further down the thread.

Reproduce it. Then fix the cause. Then prove the fix with a test that fails
without your change, and say in one line why the change is correct rather than
merely sufficient.

Deliver as: branch. For a branch, use a descriptive name and one commit
message that explains the WHY, not the diff. For a patch, hand back a file that
applies cleanly. For an explanation, write the plan and the reasoning and change
nothing.

If the issue is unclear, underspecified, or you disagree that it is a bug, say
that instead of guessing. A wrong fix costs more than a question.
Use Fix a GitHub issueOpens with everything above already filled in.

Why this works

An issue fixed from its title alone solves the wrong thing. This reproduces first, which is also what tells you whether the fix worked.

More code skills

  • idapt Code
  • Fix a failing test

Use it now in a chat in 1 click

Use Fix a GitHub issue
Find security bugs
  • Ship a feature
  • Speed up slow code
  • Untangle a god function