← 返回
未分类 中文

lazyGithub Bootstrap

Publish, bootstrap, or tidy a GitHub repository so the README and full GitHub About metadata stay in sync. Use when an agent is asked to create a new repo, p...
发布、引导或整理 GitHub 仓库,使 README 与完整的 GitHub About 元数据保持同步。当代理需要创建新仓库、推送更改或更新仓库元数据时使用。
hanjo92 hanjo92 来源
未分类 clawhub v0.1.1 1 版本 100000 Key: 无需
★ 0
Stars
📥 104
下载
💾 0
安装
1
版本
#latest

概述

GitHub Repo Bootstrap

Create a repo with both code/docs and metadata, not just the remote shell.

Workflow

  1. Inspect local project files first.
    • Read README.md if present.
    • Read package metadata (package.json, pyproject.toml, etc.) if present.
    • Infer a short project summary and 3-5 relevant topics from the project itself.
  2. Ensure these fields are set:
    • repository name
    • visibility (public or private)
    • description
    • homepage if available
    • topics
  3. If information is missing, ask for only the missing decision that cannot be inferred safely.
  4. Create or update the repo with GitHub CLI.
    • Create: gh repo create ... --description ... [--homepage ...]
    • Topics: gh repo edit ... --add-topic ...
  5. Verify the result by reading back repo metadata with gh repo view --json name,description,homepageUrl,repositoryTopics,url or gh api.
  6. If verification shows zero topics, do not declare success. Infer better topics, update the repo, and verify again. Only stop if there is a real blocker you can name.

Rules

  • Treat GitHub About as the combination of:
  • description
  • homepage / website
  • topics
  • Do not stop after setting only description.
  • Topics are mandatory by default.
  • Prefer 3-5 concise lowercase topics.
  • Avoid generic filler topics like code, app, or project unless they are truly useful.
  • Keep the description to one sentence.
  • If README is missing, create a minimal one before publishing.
  • If the user says “fill the about section,” interpret that as description + homepage + topics.
  • Treat an empty repositoryTopics result during verification as a failed task state, not a soft warning.

Topic Heuristics

Derive topics from:

  • primary language or framework
  • deployment target or platform
  • project type (cli, library, automation, bot, tooling, etc.)
  • domain keywords from README

Good examples:

  • cli,github,automation
  • typescript,react,chrome-extension
  • python,fastapi,api

Commands

Create repo:

gh repo create <name> --public --description "<summary>"

Add homepage and topics:

gh repo edit <owner>/<repo> \
  --homepage "<url>" \
  --add-topic topic1 \
  --add-topic topic2 \
  --add-topic topic3

Verify:

gh repo view <owner>/<repo> --json name,description,homepageUrl,repositoryTopics,url

Verification passes only if repositoryTopics is non-empty.

Resources

  • Prompt templates: read references/prompt-templates.md when the user wants a reusable prompt for Codex, Claude, or another agent.
  • Wrapper script: use scripts/lazygithub.sh when a single command is faster than repeated manual gh commands.

版本历史

共 1 个版本

  • v0.1.1 当前
    2026-06-04 14:21

安全检测

腾讯云安全 (Keen)

队列中

腾讯云安全 (Sanbu)

队列中

🔗 相关推荐

ai-agent

self-improving agent

pskoett
捕获经验教训、错误及修正内容,以实现持续改进。适用于以下场景:(1)命令或操作意外失败;(2)用户纠正Claude(如“不,那不对……”“实际上……”);(3)用户请求的功能不存在;(4)外部API或工具出现故障;(5)Claude发现自身
★ 4,082 📥 811,246
ai-agent

Self-Improving + Proactive Agent

ivangdavila
自我反思+自我批评+自我学习+自组织记忆。智能体评估自身工作、发现错误并持续改进。
★ 1,379 📥 320,577
ai-agent

Skill Vetter

spclaudehome
AI智能体技能安全预审工具。安装ClawdHub、GitHub等来源技能前,检查风险信号、权限范围及可疑模式。
★ 1,227 📥 267,952