Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Proposal: add a pointer to chsrc-skill (Agent Skill) in the README

オープン
  • 何か問題がありますか？
#397 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
1/5
見積もり時間
1時間未満
初心者へのやさしさ
22/100
issue の種類
ドキュメント
明瞭さ
おおむね明確
活発さ
活発
技術スタック
c, debian
領域
documentation

調査の方向性

This is a proposal to add a one-line pointer to a third-party Agent Skill, so the first step is the maintainer's decision, not an edit. Look at the README and the doc/ directory to see where third-party tooling is currently listed. Done means the maintainer has explicitly chosen the README or doc/ location, or declined. The apt dry-run bypass is a separate issue, #396, and is out of scope here.

索引モデルが issue の本文から書いたものです。

説明

Summary

I built chsrc-skill, an Agent Skill that teaches an LLM how to use chsrc correctly, and I'd like to propose including a pointer to it in the README.

Repository: https://github.com/Swcmb/chsrc-skill

What it is

SKILL.md plus 10 reference documents, all fact-checked against the chsrc v0.2.7.2 source. It contains no chsrc source code.

The premise: using chsrc correctly requires knowing details that are easy for a model to get wrong.

Behaviors that are easy to get wrong

Measured while building this (35 scenarios, 135 assertions):

Behavior What happens if you do not know it
CLI options must precede the dish name chsrc get pip -no-color → "暂不支持的换源菜品", exit code 2
-scope accepts both -scope=system and -scope system the = form silently fails on some shells
-local is deprecated prints a deprecation warning; use -scope=project
71 dishes, grouped pl_ / os_ / wr_; combo dishes operate per sub-dish py_group looks like a single target
chsrc ls lists mirror sites, chsrc list <dish> lists one dish they read as interchangeable
Old chsrc versions print the config instead of writing it the correct first move is to upgrade chsrc, not to hand-edit
On Windows the home directory is USERPROFILE, not HOME setting HOME as isolation has no effect
With no -scope, the dish decides -scope=user on an apt dish is rejected with exit code 4

Evaluation

Two configurations, same 35 prompts:

Configuration Assertions passed
With the skill 135/135 (100%)
Without the skill 108/134 (80.6%)

The prompt set covers trigger positives and negatives, six platform-detection scenarios, the bootstrap deadlock, scope safety, container boundaries, and rollback.

A finding along the way

Building this surfaced a dry-run bypass in the apt recipe, already reported separately: #396.

ensure_debian_or_ubuntu_old_sourcelist() writes /etc/apt/sources.list with a raw fopen, bypassing the in_dry_run_mode() guard in chsrc_overwrite_file(). On a Debian-family system without that file, chsrc set -dry debian writes to disk. The sibling DEB822 branch goes through chsrc_run() and honors -dry; only the legacy path does not.

Proposal

A one-line addition to the README pointing at the skill, for anyone driving chsrc through an LLM. I am happy to adjust the wording, the location, or the format.

If you would prefer not to list third-party tooling in the README, an alternative would be a line in doc/ instead. Either way I would rather have your explicit call than assume.

Note on scope

This repository contains only the Skill. It does not track your releases, does not vendor your source, and carries no code from the project.

主要言語
C
スター
6.9k
フォーク
285
30日以内にマージされた PR はありません

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

RubyMetric/chsrc のほかの issue

RubyMetric/chsrc の issue をすべて見る

似ている issue

C の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。