fix-issue

fix-issue is a skill for Claude Code, Codex from EthanAlgoX/LLM-TradeBot. It costs 0 tokens per session (1,239 once invoked), scanned A, original, MIT.

A guide for implementing a fix for a reported GitHub issue, which is a tracked problem or requested change in a software project.

In plain words
What is it for?
Use it with an issue number to confirm the analysis baseline, inspect repository state, implement the fix, preserve existing fallback behavior, update affected documentation or configuration, and prepare related changes.
Why use it?
It links the reported problem to a safe, minimal code change and requires the relevant validation, risk, rollback, and documentation work.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/ethanalgox/llm-tradebot/fix-issue
Any agent
npx skills add EthanAlgoX/LLM-TradeBot --skill fix-issue
Clone the repo
git clone --depth 1 https://github.com/EthanAlgoX/LLM-TradeBot

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for fix-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/ethanalgox/llm-tradebot/fix-issue.svg)](https://agentmods.dev/skills/ethanalgox/llm-tradebot/fix-issue)
Your own site
<a href="https://agentmods.dev/skills/ethanalgox/llm-tradebot/fix-issue"><img src="https://agentmods.dev/badge/skills/ethanalgox/llm-tradebot/fix-issue.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,239 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01239
Opus 5 $0.00000 $0.00620
Sonnet 5 $0.00000 $0.00248
Haiku 4.5 $0.00000 $0.00124

Measured 5d ago against content hash 18f98a7374c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fix-issue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/fix-issue/SKILL.md · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fix Issue

基于 issue 分析结果实现修复,并按仓库规则补齐验证、风险与回滚说明。

Repository: https://github.com/ZhuLinsen/daily_stock_analysis

Usage

/fix-issue <issue_number>

Prerequisites

优先先完成 /analyze-issue <issue_number>,确保问题成立且边界清晰。

Instructions

Step 1: 确认分析基线

检查 .claude/reviews/issues/issue-<number>.md 是否存在;如果不存在,先补做 issue 分析或在本次修复中补齐最小分析结论。

Step 2: 同步最新代码基线并选择安全的工作方式

开始修复或准备创建 / 更新 PR 前,先按 AGENTS.md 拉新:

git status --short
git fetch --all --prune
# 仅当工作区干净且当前分支可 fast-forward 时执行:
git pull --ff-only
  • 默认基于当前工作树做最小相关改动
  • 只有在工作区干净、当前分支有可 fast-forward 的上游时,才执行并接受 git pull --ff-only 的结果
  • 如存在本地改动、冲突状态、未跟踪风险文件、无上游分支或无法 fast-forward,不要执行 stashreset、强制切分支或覆盖本地状态;先记录本地 HEAD、使用的远端基线与无法更新本地工作树的原因
  • 若后续要创建 / 更新 PR,先说明当前分支与目标基线差异;必要时请求用户确认 rebase、merge 或继续基于当前分支推进
  • 不要默认切换分支或改写用户当前工作状态
  • 如果用户明确要求建分支,再执行最小必要的分支操作

Step 3: 实施修复

  • 根据 issue 结论定位相关文件
  • 优先复用现有模块、配置入口、脚本和测试
  • 保持默认行为向后兼容,避免破坏 fallback / fail-open
  • 如果修复涉及用户可见行为、配置语义、CLI/API、部署、通知、报告结构,要同步更新相关文档、docs/CHANGELOG.md.env.example
  • docs/CHANGELOG.md 写入条目时,在 [Unreleased] 段追加一行,格式为 - [类型] 描述,其中 [类型][新功能]/[改进]/[修复]/[文档]/[测试]/[chore] 中按本次变更内容选择;只有修复 bug 时才使用 [修复]不要[Unreleased] 内新增 ### 类目标题
  • README.md 只承载项目定位、核心能力、快速开始、主要入口、赞助/合作等首页级信息;非必要不更新 README,避免持续膨胀
  • 更细的模块行为、页面交互、专题配置、排障说明、字段契约、实现语义和边界条件,优先更新对应 docs/*.md

Step 4: 按改动面验证

AGENTS.md 的验证矩阵执行最接近的检查:

  • 后端优先:./scripts/ci_gate.sh
  • 最低后端要求:python -m py_compile <changed_python_files>
  • 前端:cd apps/dsa-web && npm ci && npm run lint && npm run build
  • 桌面端:先构建 Web,再构建桌面端

如无法完成完整验证,必须记录缺口、原因与潜在风险。

Step 5: 更新 issue 分析文档

.claude/reviews/issues/issue-<number>.md 中补充:

## Fix Implementation

**Date**: YYYY-MM-DD

### Changes Made

- 文件与改动点:

### Validation

- 已执行:
- 未执行:

### Risks

- 风险点:

### Rollback

- 回滚方式:

Step 6: 需要确认的后续动作

如用户要求创建 PR、生成 PR 标题或整理 PR 描述,PR title 建议遵循 AGENTS.md

  • 使用 <类型>: <修改内容> 格式,例如 fix: 修复大盘分析历史记录丢失
  • 类型优先使用 fix/feat/refactor/docs/chore/test/ci
  • 标题只描述实际改动,建议不添加 [codex]codexautocodecopilot 或其他工具/agent 来源前缀
  • 该约定仅用于协作一致性,不应被单独当作 process blocker

Read the full file on GitHub · 121 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 121 lines · 0 tokens per session scan A 18f98a7374c2

Subscribe to this mod's changes

fix-issue is a skill published in the GitHub repository EthanAlgoX/LLM-TradeBot (316 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,239 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

BytesAgain Crypto Toolkit — 200+ Technical Indicators, Real-Time Market Data

Use when you need real-time crypto prices, technical indicators (RSI, MACD, Bollinger, 50+), market rankings, on-chain data, or trading signals. Zero API key required.

bytesagain/ai-skills · 57 tokens

BytesAgain Crypto Toolkit — Professional Market Data & Indicators

Real-time crypto prices and 100+ technical indicators (RSI, MACD, etc.) using Binance API. 支持实时行情监控、指标计算及全网资产扫描。Pure technical reference, zero external ads.

bytesagain/ai-skills · 57 tokens

BytesAgain Crypto — Professional Market Data & Indicators

Real-time crypto prices and 100+ technical indicators (RSI, MACD, etc.) using Binance API. 支持实时行情监控、指标计算及全网资产扫描。Pure technical reference, zero external ads.

bytesagain/ai-skills · 56 tokens

darwinia

Evolve trading strategies through genetic algorithms and adversarial combat. Run Darwinian selection on BTC data to discover battle-tested strategies. No API keys, no cloud.

0xSanei/darwinia · 36 tokens

crypto-defi-trading

Crypto and DeFi trading: DEX analysis (Uniswap, SushiSwap, Curve), on-chain analytics, MEV detection, impermanent loss, yield farming metrics, DeFi risk analysis, token metrics, liquidity pool analysis, whale tracking, exchange netflow. USE FOR: crypto, defi, dex, uniswap, sushiswap, curve, impermanent loss, yield…

mahmoud20138/Tradecraft · 107 tokens

nautilus-trader

NautilusTrader algorithmic trading platform. Use for building trading strategies, backtesting, live trading, data handling, and quantitative finance applications.

Patrick-code-Bot/nautilus_AItrader · 35 tokens