npx skills add https://github.com/alfredang/skills --skill 'GitHub About'/github-about 或 github-about
Git 与仓库
github about, repo description, github topics, live site url, homepage url, repo setup, github metadata, repo settings, github description, add topics, set homepage, repo about, github profile, project metadata, update about, update repo, update github, update description, set topics, repo about section, about section, update repo about, update github about
通过分析您的代码库,自动更新 GitHub 仓库的“关于”部分——包括描述、实时网站 URL 和主题。无需手动设置仓库。
此技能使用 Claude Code 订阅计划 运行。请勿使用按量付费的 API 密钥。所有 AI 操作都应在具有活跃订阅的 Claude Code CLI 环境中执行。
重要:自动触发行为 当用户提出以下要求时,应自动调用此技能(无需用户输入 /github-about):
当自动触发时,静默运行完整工作流,并在最后报告结果。
在运行任何 gh 命令之前,始终加载令牌:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
source ~/.zshrc 2>/dev/null
这会加载 GH_TOKEN,gh CLI 会自动使用它进行身份验证。必须在每次执行开始时完成此操作。
我将更新您 GitHub 仓库的“关于”部分!
工作流程包括:
| 步骤 | 描述 |
|---|---|
| 环境设置 | 加载 ~/.zshrc 以设置 GH_TOKEN |
| 身份验证检查 | 通过令牌验证 gh CLI 身份验证 |
| 仓库信息 | 从 git remote 中提取所有者/仓库信息 |
| 描述 | 生成并设置引人注目的仓库描述 |
| 实时网站 | 检测并设置实时网站 URL |
| 主题 | 分析技术栈并添加相关主题 |
执行 /github-about 时,请遵循此工作流程:
gh --version
如果未安装,请通知用户:
ERROR: GitHub CLI (gh) not found.
Install: https://cli.github.com/
GH_TOKEN 环境变量已在 ~/.zshrc 中配置。gh CLI 在 GH_TOKEN 存在时会自动使用它——无需浏览器登录。
身份验证检查顺序:
source ~/.zshrc 2>/dev/null
echo "GH_TOKEN is set: ${GH_TOKEN:+yes}"
2. 验证其是否有效:
gh auth status
3. 如果 GH_TOKEN 未设置且 gh auth status 失败,则回退到浏览器登录:
gh auth login --hostname github.com --git-protocol https --web
重要: 在任何 gh 命令之前始终运行 source ~/.zshrc,以确保 GH_TOKEN 加载到当前 shell 会话中。gh CLI 会自动识别 GH_TOKEN 和 GITHUB_TOKEN 环境变量——无需额外配置。
REMOTE_URL=$(git remote get-url origin)
OWNER=$(echo "$REMOTE_URL" | sed -E 's#.*(github\.com)[:/]([^/]+)/([^/.]+)(\.git)?$#\2#')
REPO=$(echo "$REMOTE_URL" | sed -E 's#.*(github\.com)[:/]([^/]+)/([^/.]+)(\.git)?$#\3#')
gh repo view --json description,homepageUrl,repositoryTopics
存储当前值,以便我们知道需要更新什么。
如果描述已设置,则跳过,除非用户明确要求更新。
分析项目以生成简短、引人注目的描述(最多 350 个字符):
分析来源(按优先级排序):
README.md — 项目标题、第一段、功能package.json → description 字段pyproject.toml → [project] descriptionCargo.toml → descriptionsetup.py 或 setup.cfg → description描述指南:
gh repo edit --description "Your generated description"
如果主页 URL 已设置,则跳过,除非用户明确要求更新。
按以下优先级顺序搜索部署 URL:
Vercel : 检查 Vercel 部署
# Check if Vercel project exists
cat .vercel/project.json 2>/dev/null
# Or check vercel.json for project name
cat vercel.json 2>/dev/null
URL 模式:https://<project-name>.vercel.app
GitHub Pages : 检查是否启用了 Pages
gh api "/repos/$OWNER/$REPO/pages" 2>/dev/null
URL 模式:https://<owner>.github.io/<repo>/
package.json : 检查 homepage 字段
node -e "console.log(require('./package.json').homepage || '')" 2>/dev/null
README.md : 扫描部署 URL
.vercel.app, .netlify.app, .github.io, .herokuapp.com, .fly.dev, .railway.app自定义域名 : 检查 CNAME 文件(GitHub Pages 自定义域名)
cat CNAME 2>/dev/null
gh repo edit --homepage "https://detected-url.com"
如果主题已设置,则添加到其中,而不是替换。切勿删除现有主题。
分析项目以确定相关主题:
语言检测:
| 文件/模式 | 主题 |
|---|---|
*.ts, *.tsx | typescript |
*.js, *.jsx | javascript |
*.py | python |
*.rs | rust |
*.go | go |
*.java | java |
*.swift | swift |
*.rb | ruby |
框架检测:
| 文件/模式 | 主题 |
|---|---|
next.config.* | nextjs, react |
vite.config.* | vite |
package.json 包含 react | react |
package.json 包含 vue | vue |
package.json 包含 svelte | svelte |
angular.json | angular |
requirements.txt 包含 django | django |
requirements.txt 包含 fastapi | fastapi |
requirements.txt 包含 flask | flask |
Cargo.toml | rust |
go.mod | golang |
tailwind.config.* | tailwindcss |
expo 在 package.json 中 | expo, react-native |
平台检测:
| 文件/模式 | 主题 |
|---|---|
.vercel/ 或 vercel.json | vercel |
Dockerfile | docker |
fly.toml | fly-io |
railway.json | railway |
.github/workflows/ | github-actions |
supabase/ | supabase |
领域检测(分析 README 和源代码):
ai, machine-learning, llmcli, command-lineapi, rest-api, graphqlweb-app, webappgame, gamedevdeveloper-tools, devtools主题指南:
react-native)code 或 projectgh repo edit --add-topic "topic1" --add-topic "topic2" --add-topic "topic3"
重要: 使用 --add-topic(而不是 --topic)以保留现有主题。
打印所有更改的摘要:
=== GitHub About Updated ===
Repository: OWNER/REPO
Description: <the description that was set>
Homepage: <the URL that was set>
Topics: topic1, topic2, topic3, topic4
View: https://github.com/OWNER/REPO
如果任何步骤被跳过(已设置),请注明:
Description: Already set (skipped)
Homepage: https://example.vercel.app (updated)
Topics: react, nextjs, typescript (added 3 new)
~/.zshrc 中的 GH_TOKEN 进行身份验证(无需浏览器登录)gh auth login运行 /github-about 后:
每周安装次数
0
仓库
GitHub 星标数
1
首次出现
1970年1月1日
安全审计
/github-about or github-about
Git & Repository
github about, repo description, github topics, live site url, homepage url, repo setup, github metadata, repo settings, github description, add topics, set homepage, repo about, github profile, project metadata, update about, update repo, update github, update description, set topics, repo about section, about section, update repo about, update github about
Automatically update your GitHub repository's About section — description, live site URL, and topics — by analyzing your codebase. No manual repo settings needed.
This skill runs using Claude Code with subscription plan. Do NOT use pay-as-you-go API keys. All AI operations should be executed through the Claude Code CLI environment with an active subscription.
IMPORTANT: Auto-trigger behavior This skill should be automatically invoked (without the user needing to type /github-about) whenever the user asks to:
When auto-triggered, run the full workflow silently and report results at the end.
Before running ANY gh commands, always source the token:
source ~/.zshrc 2>/dev/null
This loads GH_TOKEN which the gh CLI uses automatically for authentication. This MUST be done at the start of every execution.
I'll update your GitHub repo's About section!
The workflow includes:
| Step | Description |
|---|---|
| Env Setup | Source ~/.zshrc to load GH_TOKEN |
| Auth Check | Verify gh CLI authentication via token |
| Repo Info | Extract owner/repo from git remote |
| Description | Generate and set a compelling repo description |
| Live Site | Detect and set the live site URL |
| Topics | Analyze tech stack and add relevant topics |
When executing /github-about, follow this workflow:
gh --version
If not installed, inform the user:
ERROR: GitHub CLI (gh) not found.
Install: https://cli.github.com/
The GH_TOKEN environment variable is already configured in ~/.zshrc. The gh CLI automatically uses GH_TOKEN when present — no browser login needed.
Authentication check order:
source ~/.zshrc 2>/dev/null
echo "GH_TOKEN is set: ${GH_TOKEN:+yes}"
2. Verify it works:
gh auth status
3. If GH_TOKEN is not set and gh auth status fails, fall back to browser login:
gh auth login --hostname github.com --git-protocol https --web
Important: Always run source ~/.zshrc before any gh commands to ensure GH_TOKEN is loaded into the current shell session. The gh CLI respects GH_TOKEN and GITHUB_TOKEN environment variables automatically — no extra configuration needed.
REMOTE_URL=$(git remote get-url origin)
OWNER=$(echo "$REMOTE_URL" | sed -E 's#.*(github\.com)[:/]([^/]+)/([^/.]+)(\.git)?$#\2#')
REPO=$(echo "$REMOTE_URL" | sed -E 's#.*(github\.com)[:/]([^/]+)/([^/.]+)(\.git)?$#\3#')
gh repo view --json description,homepageUrl,repositoryTopics
Store the current values so we know what needs updating.
If the description is already set, skip unless user explicitly asks to update it.
Analyze the project to generate a short, compelling description (max 350 characters):
Sources to analyze (in priority order):
README.md — project title, first paragraph, featurespackage.json → description fieldpyproject.toml → [project] descriptionCargo.toml → descriptionsetup.py or setup.cfg → descriptionDescription guidelines:
gh repo edit --description "Your generated description"
If the homepage URL is already set, skip unless user explicitly asks to update it.
Search for deployment URLs in this priority order:
Vercel : Check for Vercel deployment
# Check if Vercel project exists
cat .vercel/project.json 2>/dev/null
# Or check vercel.json for project name
cat vercel.json 2>/dev/null
URL pattern: https://<project-name>.vercel.app
GitHub Pages : Check if Pages is enabled
gh api "/repos/$OWNER/$REPO/pages" 2>/dev/null
URL pattern: https://<owner>.github.io/<repo>/
package.json : Check homepage field
node -e "console.log(require('./package.json').homepage || '')" 2>/dev/null
README.md : Scan for deployment URLs
.vercel.app, .netlify.app, .github.io, .herokuapp.com, .fly.dev, .railway.appCustom domain : Check CNAME file (GitHub Pages custom domain)
gh repo edit --homepage "https://detected-url.com"
If topics are already set, add to them rather than replacing. Never remove existing topics.
Analyze the project to determine relevant topics:
Language detection:
| File/Pattern | Topic |
|---|---|
*.ts, *.tsx | typescript |
*.js, *.jsx | javascript |
*.py | python |
*.rs |
Framework detection:
| File/Pattern | Topic |
|---|---|
next.config.* | nextjs, react |
vite.config.* | vite |
package.json with react | react |
package.json with |
Platform detection:
| File/Pattern | Topic |
|---|---|
.vercel/ or vercel.json | vercel |
Dockerfile | docker |
fly.toml | fly-io |
railway.json |
Domain detection (analyze README and source):
ai, machine-learning, llmcli, command-lineapi, rest-api, graphqlweb-app, webappgame, Topic guidelines:
react-native)code or projectgh repo edit --add-topic "topic1" --add-topic "topic2" --add-topic "topic3"
Important: Use --add-topic (not --topic) to preserve existing topics.
Print a summary of all changes made:
=== GitHub About Updated ===
Repository: OWNER/REPO
Description: <the description that was set>
Homepage: <the URL that was set>
Topics: topic1, topic2, topic3, topic4
View: https://github.com/OWNER/REPO
If any step was skipped (already set), note it:
Description: Already set (skipped)
Homepage: https://example.vercel.app (updated)
Topics: react, nextjs, typescript (added 3 new)
GH_TOKEN from ~/.zshrc (no browser login needed)gh auth login if token is unavailableAfter running /github-about:
Weekly Installs
0
Repository
GitHub Stars
1
First Seen
Jan 1, 1970
Security Audits
agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试
147,400 周安装
cat CNAME 2>/dev/null
rust |
*.go | go |
*.java | java |
*.swift | swift |
*.rb | ruby |
vuevue |
package.json with svelte | svelte |
angular.json | angular |
requirements.txt with django | django |
requirements.txt with fastapi | fastapi |
requirements.txt with flask | flask |
Cargo.toml | rust |
go.mod | golang |
tailwind.config.* | tailwindcss |
expo in package.json | expo, react-native |
railway.github/workflows/ | github-actions |
supabase/ | supabase |
gamedevdeveloper-tools, devtools