Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

rails-bug-triageRails BUG triage 搜索

Agent Skill

rails-bug-triage 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

499

周安装

20

GitHub Stars

15

下载量

162
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:rails-bug-triage(Rails BUG triage 搜索)
来源仓库:https://github.com/igmarin/rails-agent-skills
仓库路径:skills/rails-bug-triage
安装命令:
npx skills add https://github.com/igmarin/rails-agent-skills --skill rails-bug-triage
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/igmarin/rails-agent-skills --skill rails-bug-triage

简介

用于分类与优先级排序 Rails 项目中的 Bug 报告与 Issue。

  • 适合在团队协作中快速分配修复责任与跟进解决进度。
  • 通过 GitHub 安装,可结合标签系统与历史记录自动归类新 Issue。
  • 应避免仅凭标题判断严重程度,需查看复现步骤与环境影响。
  • 建议建立标准化分类规则,提升处理效率与透明度。rails-bug-triage 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Rails Bug Triage

Use this skill when a bug report exists but the right reproduction path and fix sequence are not yet clear.

Core principle: Do not guess at fixes. Reproduce the bug, choose the right failing spec, then plan the smallest safe repair.

Process

  1. Capture the report: Restate the expected behavior, actual behavior, and reproduction steps.
  2. Bound the scope: Identify whether the issue appears in request handling, domain logic, jobs, engine integration, or an external dependency.
  3. Gather current evidence: Logs, error messages, edge-case inputs, recent changes, or missing guards.
  4. Choose the first failing spec: Pick the boundary where the bug is visible to users or operators.
  5. Define the smallest fix path: Name the likely files and the narrowest behavior change that should make the spec pass.
  6. Hand off: Continue through rails-tdd-slices -> rspec-best-practices -> implementation skill.

Triage Output

Return findings in this shape:

  1. Observed behavior
  2. Expected behavior
  3. Likely boundary
  4. First failing spec to add
  5. Smallest safe fix path
  6. Follow-up skills

Example (wrong status code bug):

1. Observed:  POST /orders returns 500 when product is out of stock
2. Expected:  Returns 422 with { error: "Out of stock" }
3. Boundary:  Request layer — visible in HTTP contract
4. First spec: spec/requests/orders/create_spec.rb
5. Fix path:  Orders::CreateOrder should return { success: false, error: "Out of stock" }
              when inventory check fails; controller renders 422
6. Next:      rails-tdd-slices → write request spec → rspec-best-practices → fix

Skeleton failing spec:

# spec/requests/orders/create_spec.rb
RSpec.describe "POST /orders", type: :request do
  context "when product is out of stock" do
    let(:product) { create(:product, stock: 0) }

    it "returns 422 with an error message" do
      post orders_path, params: { order: { product_id: product.id, quantity: 1 } }, as: :json
      expect(response).to have_http_status(:unprocessable_entity)
      expect(response.parsed_body["error"]).to eq("Out of stock")
    end
  end
end

Run it before implementing the fix: bundle exec rspec spec/requests/orders/create_spec.rb

Boundary Guide

See BOUNDARY_GUIDE.md for the full bug-shape → spec-type mapping and layer diagnosis tips.

Quick reference:

Bug shapeLikely first spec
HTTP symptoms (status, JSON, redirect)Request spec
Data symptoms (wrong value, validation)Model or service spec
Timing symptoms (missing job, email)Job spec
Engine routing/generator regressionEngine spec in dummy app

Pitfalls

PitfallWhat to do
Unit spec when the bug is visible at request levelStart where the failure is actually observed
Bundling reproduction, refactor, and new featuresFix the bug in the smallest safe slice only
Flaky evidence treated as green light to patchStabilize reproduction before touching code
The explanation relies on "probably" or "maybe"Ambiguity means the reproduction step isn't done yet

Integration

SkillWhen to chain
rails-tdd-slicesTo choose the strongest first failing spec for the bug
rspec-best-practicesTo run the TDD loop correctly after the spec is chosen
refactor-safelyWhen the bug sits inside a risky refactor area and behavior must be preserved first
rails-code-reviewTo review the final bug fix for regressions and missing coverage
rails-architecture-reviewWhen the bug points to a deeper boundary or orchestration problem

Assets

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.75%
按下载量换算61

Claude

29%
按下载量换算47

Cursor

19.63%
按下载量换算32

Gemini CLI

9.68%
按下载量换算16

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills