bug fix

AI Community

Skill notes

Phase 1: Understand

Read the issue body carefully. Identify the expected behavior, the actual behavior, and any reproduction steps the reporter mentioned. Inspect the project layout: read package.json, README.md, and AGENTS.md if present. Identify the test framework (vitest, jest, node:test, tsx test runner, etc.) and the test command. Locate the source file(s) most likely involved in the bug. Read them fully — do not skim.

Phase 2: Reproduce

Create a new git branch named flue/fix-issue-{{issueNumber}}. Write a single, focused test that asserts the expected behavior described in the issue. The test must currently fail because of the bug. Run the test command. The test must fail. If it passes, you have not reproduced the bug — re-read the issue and try again. Save the failing test output. You will reference it in the PR body.

Phase 3: Fix

Make the minimal code change required to make the failing test pass. Do not refactor unrelated code. Do not reformat untouched files. Do not edit lockfiles. Run the full test suite. All tests must pass, including pre-existing ones.

Phase 4: Pull Request

Stage and commit the changes with a clear conventional-style message: fix: <one-line summary> (#{{issueNumber}}) Push the branch to the fork ({{repo}}): git push origin flue/fix-issue-{{issueNumber}}. Open a pull request against the fork's own default branch (not upstream). Pin both --repo and --base explicitly so gh doesn't accidentally target {{issueRepo}}: Use this PR body structure:

Output

Return a structured result with these fields: branch: the branch name you created prUrl: the URL of the pull request you opened testFile: the path of the test file you added or modified filesChanged: the array of file paths you changed (relative to repo root)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@daytonaio · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Understand

Read the issue body carefully. Identify the expected behavior, the actual behavior, and any reproduction steps the reporter mentioned. Inspect the project layout: read `package.json`, `README.md`, and `AGENTS.md` if present. Identify the test framework (vitest, jest, node:test, tsx test runner, etc.) and the test command. Locate the source file(s) most likely involved in the bug. Read them fully — do not skim.

02
Phase 2: Reproduce

Create a new git branch named `flue/fix-issue-{{issueNumber}}`. Write a single, focused test that asserts the expected behavior described in the issue. The test must currently fail because of the bug. Run the test command. The test must fail. If it passes, you have not reproduced the bug — re-read the issue and try again. Save the failing test output. You will reference it in the PR body.

03
Phase 3: Fix

Make the minimal code change required to make the failing test pass. Do not refactor unrelated code. Do not reformat untouched files. Do not edit lockfiles. Run the full test suite. All tests must pass, including pre-existing ones.

04
Phase 4: Pull Request

Stage and commit the changes with a clear conventional-style message: `fix: <one-line summary> (#{{issueNumber}})` Push the branch to the fork (`{{repo}}`): `git push origin flue/fix-issue-{{issueNumber}}`. Open a pull request against the fork's own default branch (not upstream). Pin both `--repo` and `--base` explicitly so `gh` doesn't accidentally target `{{issueRepo}}`: Use this PR body structure:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.