跳到正文
cccskills
免费在 GitHub 公开

skillsaw-issue

Use when skillsaw reports a likely false positive, misses an edge case, behaves incorrectly, or needs an RFE. Gather a safe report and, only with explicit user permission, create a feedback bundle or open a GitHub issue.

中文简介正在准备中。当前显示原文说明。

集成工具GitHub
查看安装方法

包含的文件(1)

  • SKILL.md3.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

skillsaw Issue

Use this skill when skillsaw itself needs a GitHub issue: a false positive, a missed violation, a crash, incorrect autofix, an edge case in rule detection, or a request for enhancement (RFE). Do not use it to report a problem in the repository being linted unless that problem demonstrates incorrect skillsaw behavior or a useful feature gap.

Gather safe evidence first

Collect the minimum evidence needed to explain the issue without sending anything externally:

  • skillsaw version and the exact command
  • affected rule ID, file type, and relevant configuration
  • expected behavior and actual behavior for a bug
  • user goal and proposed outcome for an RFE
  • a minimal reproducer or a short sanitized excerpt

Never copy credentials, private repository content, or complete diagnostic output into an issue draft. Prefer a minimal synthetic reproducer.

Require separate permission for each external action

Ask the user two explicit questions before taking either action:

  1. "May I run skillsaw feedback to create a local diagnostic ZIP?"
  2. "May I open an issue in stbenjam/skillsaw?"

Do not run skillsaw feedback without permission for the first action. Do not create a GitHub issue without permission for the second action. Permission for one action does not authorize the other. If permission is absent, present a sanitized draft and ask for the missing approval.

Create a feedback bundle only when approved

Run skillsaw feedback <repository-path> with a concise --message that describes the observed behavior. The command creates a local ZIP; it does not submit anything. Do not add --include unless the user explicitly identifies the file to share.

Review the ZIP before sharing it. skillsaw does not scan file contents for secrets: anything --include or --config names is copied in verbatim, so read those files yourself and remove or replace anything sensitive. Keep the bundle local if the user does not also approve opening an issue.

Open an issue only when approved

Search existing issues first to avoid duplicates. Then open an issue in stbenjam/skillsaw with:

  • a specific title naming the affected rule, behavior, or requested capability
  • the minimal reproducer and exact command for a bug
  • expected and actual results for a bug, or the user goal and proposed outcome for an RFE
  • skillsaw version and relevant configuration when applicable
  • the reviewed feedback ZIP only when the user approves attaching it

State which sensitive details were omitted. Link the issue back to the user and summarize what was shared. Do not change labels, milestones, assignees, or project state unless the user specifically requests it.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Create a skillsaw rule plugin — a pip-installable Python package that adds custom lint rules to skillsaw. Walks through scaffolding the package, writing rules against the lint tree, testing, and publishing to PyPI. Use when a user wants to share skillsaw rules across repositories or publish them for others.

中文简介正在准备中。当前显示原文说明。

stbenjam/skillsaw672026年10月17日 更新

Survey the AI coding assistant and agentic tool ecosystem, assess skillsaw's competitive position, identify emerging patterns and missing capabilities, and produce a prioritized strategic report as a GitHub issue. Use when evaluating ecosystem trends and product gaps.

中文简介正在准备中。当前显示原文说明。

stbenjam/skillsaw672026年10月17日 更新

Fix skillsaw lint violations — apply deterministic autofixes, then resolve the remaining violations with targeted edits guided by `skillsaw explain`. Use when skillsaw reports violations, when asked to clean up lint findings, or after `skillsaw fix` leaves violations behind.

中文简介正在准备中。当前显示原文说明。

stbenjam/skillsaw672026年10月17日 更新

Pick up open GitHub issues from collaborators and create PRs to solve them. Use when triaging and resolving reported bugs or feature requests.

中文简介正在准备中。当前显示原文说明。

stbenjam/skillsaw672026年10月17日 更新

Triage a GitHub issue filed against skillsaw — classify it (bug, feature, docs, question, other), verify its claims against the codebase, enrich it with missing details, and post one structured triage comment. Use when triaging and labeling incoming issues, not to fix them.

中文简介正在准备中。当前显示原文说明。

stbenjam/skillsaw672026年10月17日 更新

Use when modifying agentic contextual building blocks like skills (SKILL.md), slash commands, agents, hooks, plugins, marketplaces, and instruction files (CLAUDE.md, AGENTS.md, GEMINI.md, QWEN.md, Cursor, Copilot, Cline, or Kiro rules), tool configuration such as an OpenCode `opencode.json`, Muse Code hooks (`.muse/hooks.json`), a Grok Build `.grok/` project layer or a Google Antigravity customization root (`.agents/`, `.agent/`, `_agents/`, `_agent/` — hooks, MCP config, rules, registries and plugins), and committed project memory (`.agents/memory/`). Run skillsaw on the files you touched, apply autofixes, resolve remaining violations with `skillsaw explain` guidance, and re-lint until clean before considering the work complete.

中文简介正在准备中。当前显示原文说明。

stbenjam/skillsaw672026年10月17日 更新

查看 stbenjam 的全部技能

报告此技能的问题