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

apply-all-findings应用所有调查结果

Agent Skill

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

总安装

480

周安装

20

GitHub Stars

6

下载量

160
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:apply-all-findings(应用所有调查结果)
来源仓库:https://github.com/troykelly/claude-skills
仓库路径:skills/apply-all-findings
安装命令:
npx skills add https://github.com/troykelly/claude-skills --skill apply-all-findings
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/troykelly/claude-skills --skill apply-all-findings

简介

用于查找、检索和筛选相关信息。apply-all-findings 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

  • 适合根据关键词快速定位候选结果。
  • 通过 GitHub 安装,需确认权限和维护状态。
  • 可能触发联网或文件读写,建议提前评估风险。
  • 适用于 Codex、Claude、Cursor 和 Gemini CLI。

SKILL.md

Apply All Findings

Overview

Address EVERY finding from code review. Findings are either FIXED or DEFERRED with tracking issues.

Core principle: Minor issues accumulate into major problems.

The rule: If it was worth noting, it's worth tracking.

ABSOLUTE REQUIREMENT: Every finding results in ONE of:

  1. Fixed in this PR (verified)
  2. Tracking issue created (linked in review artifact)

There is NO third option. "Won't fix without tracking" is NOT permitted.

Why All Findings

Minor Issues Compound

1 unclear variable name +
1 missing null check +
1 inconsistent style +
1 outdated comment =
Confusing, fragile code

Selective Fixing Creates Precedent

"This minor issue can wait" →
"That minor issue can wait too" →
"We don't fix minor issues" →
Technical debt mountain

Thoroughness Builds Quality Culture

Every finding addressed →
High standards maintained →
Quality becomes habit

The Process

Step 1: Gather All Findings

From comprehensive-review, you have:

### Findings

1. [Critical] SQL injection in findUser()
2. [Major] N+1 query in getOrders()
3. [Minor] Variable 'x' should be renamed
4. [Minor] Missing JSDoc on helper()
5. [Minor] Inconsistent quote style

Step 2: Create Checklist

Every finding becomes a todo:

- [ ] Fix SQL injection in findUser()
- [ ] Fix N+1 query in getOrders()
- [ ] Rename variable 'x' to descriptive name
- [ ] Add JSDoc to helper()
- [ ] Fix quote style to use single quotes

Step 3: Address Systematically

Work through the list. For each finding:

If Fixable:

  1. Fix the issue
  2. Verify the fix
  3. Check off the item
  4. Move to next finding

If Not Fixable in This PR:

  1. Verify valid deferral reason (see deferred-finding skill)
  2. Create tracking issue with full documentation
  3. Add tracking issue to review artifact
  4. Mark as DEFERRED (not unaddressed)
  5. Move to next finding
# Create tracking issue for deferred finding
gh issue create \
  --title "[Finding] [Description] (from #123)" \
  --label "review-finding,depth:1" \
  --body "[Full deferred-finding template]"

# Create spawned-from label if needed
gh label create "spawned-from:#123" --color "C2E0C6" 2>/dev/null || true
gh issue edit [NEW_ISSUE] --add-label "spawned-from:#123"

Step 4: Verify All Complete

Before considering done:

# Re-run linting
pnpm lint

# Re-run tests
pnpm test

# Re-run type check
pnpm typecheck

All checks must pass.

Step 5: Update Review Artifact

After all findings addressed, update artifact in issue comment:

  1. All FIXED findings marked ✅ FIXED
  2. All DEFERRED findings have tracking issue # linked
  3. "Unaddressed: 0" in summary
  4. "Review Status: COMPLETE"

Addressing by Type

Critical/Major Findings

These require code changes:

// Finding: SQL injection in findUser()
// Before
return db.query(`SELECT * FROM users WHERE username = '${username}'`);

// After
return db.query('SELECT * FROM users WHERE username = ?', [username]);

Minor: Naming

// Finding: Variable 'x' should be renamed
// Before
const x = users.filter(u => u.active);

// After
const activeUsers = users.filter(user => user.isActive);

Minor: Documentation

// Finding: Missing JSDoc on helper()
// Before
function helper(data: Data): Result {

// After
/**
 * Transforms raw data into the expected result format.
 *
 * @param data - Raw data from the API
 * @returns Transformed result ready for display
 */
function helper(data: Data): Result {

Minor: Style

// Finding: Inconsistent quote style
// Before
const name = "Alice";
const greeting = 'Hello';

// After (using project standard: single quotes)
const name = 'Alice';
const greeting = 'Hello';

Handling Deferrals

Valid Deferral Reasons

ReasonExampleRequires
Out of scopeArchitectural changeTracking issue
External dependencyInfrastructure changeTracking issue
Breaking changeMajor version bumpTracking issue
Separate concernIndependent featureTracking issue

NOT Valid Deferral Reasons

ExcuseRealityAction
"It's minor"Minor compoundsFix now
"Takes too long"Debt takes longerFix now
"Good enough"Never enoughFix now
"Not important"Then why note it?Fix now
"Do it later"Without tracking? No.Fix or create issue

Deferral MUST Create Issue

ABSOLUTE: No deferral without tracking issue.

# WRONG - Deferred without tracking
"We'll fix the SQL injection later"  # NO

# RIGHT - Deferred with tracking
gh issue create --title "[Finding] SQL injection in findUser (from #123)" ...
# Then link #456 in review artifact

Verification

After addressing all findings:

Run All Checks

# Linting
pnpm lint

# Type checking
pnpm typecheck

# Tests
pnpm test

# Build
pnpm build

Review the Diff

git diff

Verify:

  • All findings addressed
  • No unrelated changes
  • Tests updated if behavior changed

Self-Review Again

Quick pass through 7 criteria to ensure fixes didn't introduce new issues.

Checklist

Before moving on from review:

  • All critical findings addressed
  • All major findings addressed
  • All minor findings addressed
  • Any deferred finding has tracking issue created
  • Tracking issues linked in review artifact
  • All automated checks pass
  • Fixes reviewed for correctness
  • No new issues introduced
  • Review artifact updated with final status
  • "Unaddressed: 0" confirmed

Common Pushback (Rejected)

PushbackResponse
"We can fix minors later"Without tracking? No. Create issue or fix now.
"This is slowing us down"Debt slows you down more.
"It's not important"Then why was it noted?
"Good enough"Good enough is never enough.
"The reviewer is being picky"Attention to detail is valuable.

Integration

This skill is called by:

  • issue-driven-development - Step 10

This skill follows:

  • comprehensive-review - Generates the findings

This skill uses:

  • deferred-finding - For creating tracking issues

This skill ensures:

  • No accumulated minor issues
  • Consistent quality standards
  • Complete reviews, not partial
  • All deferrals tracked in GitHub

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

Claude Code

30.96%
按下载量换算50

Antigravity

22.41%
按下载量换算36

Gemini CLI

16.44%
按下载量换算26

OpenCode

12.79%
按下载量换算20

Cursor

7.4%
按下载量换算12

kiro-cli

3.97%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills