脚手架新仓库
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- macOS
- 运行环境要求
- Python
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 读取环境变量
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Scaffold New Repo
Generate the language-agnostic foundation files that every new repository starts with.
## Workflow
### 1. Gather Project Information
If the user provided a project name in their request, use it directly instead of detecting from git remote or README. If they specified a project type (one of `go-cli`, `go-library`, `javascript`, `pascal`, `python`, `ruby`, `rust`, `shell`, `swift`, `zig-cli`, `generic`), use it instead of inferring from `.gitignore`. Any remaining parameters should still be gathered normally.
Derive what you can automatically, then ask for only what's missing:
- **Project name** -- derive from the git remote URL or `README.md` h1 heading, not from the directory or branch name (those are often misleading, e.g. worktree paths). Detection order:
1. `git remote get-url origin` -- extract the repo name from the URL (strip the trailing `.git` if present, take the last path segment). If the command exits non-zero, returns empty output, or the URL cannot be parsed into a repo name, treat this as "no remote" and continue to step 2.
1. If there is no usable remote, check for an existing `README.md` and use its h1 heading (converted to kebab-case)
1. Only if both the remote and README detection fail, ask the user for the project name
- **Short description** -- ask the user for a one-sentence description.
- **Project type** -- check the existing `.gitignore` first (GitHub often generates one when creating the repo). Infer the project type from its contents:
Check heuristics in the order listed below. The first match wins.
- `go.work` or `*.test` → Go CLI or Go library
- `node_modules/` → JavaScript
- `__pycache__/` or `*.pyc` → Python
- `*.gem` or `.bundle/` → Ruby
- `*.ppu` or `*.compiled` → Pascal
- `xcuserdata/` alone, or both `.build/` and `*.ipa` together → Swift
- `.zig-cache/` or `zig-out/` → Zig CLI
- `target/` with no other language markers matched → Rust
- Minimal or macOS-only entries → Shell or Generic
- Only ask the user for the project type if the `.gitignore` does not make it clear.
- **Project type options**: Go CLI, Go library, JavaScript, Pascal, Python, Ruby, Rust, Shell, Swift, Zig CLI, Generic
### 2. Detect User Identity
Detect the user's GitHub username and full name for use in templates:
```bash
# GitHub username (for module paths, URLs, clone commands)
gh api user -q .login
```
```bash
# Full name (for LICENSE copyright)
git config user.name
```
If either command fails or returns empty output, ask the user to provide the value. Use the GitHub username wherever templates reference `GITHUB-USERNAME` and the full name wherever they reference `COPYRIGHT-HOLDER`.
### 3. Prepare the Directory
If the current directory is empty or the user specifies a directory name:
```bash
mkdir -p PROJECT-NAME
cd PROJECT-NAME
```
If the current directory already has files, confirm with the user before adding boilerplate alongside existing content.
### 4. Initialize Git
Skip if already inside a git repository.
```bash
git init
```
### 5. Generate LICENSE
Read `./references/license.md` for the MIT license template and create a `LICENSE` file from it.
- Replace `YEAR` with the current year (run `date +%Y` to get it)
- Replace `COPYRIGHT-HOLDER` with the detected full name
### 6. Generate README.md
Read `./references/readme.md` for the README template and create a `README.md` from it.
- Replace the heading with the exact binary or repository name (kebab-case)
- Insert the short description
- Tailor the Installation section placeholder to the project type
- Replace `GITHUB-USERNAME` with the detected GitHub username
### 7. Generate CHANGELOG.md
Read `./references/changelog.md` for the CHANGELOG template and create a `CHANGELOG.md` from it.
No replacements needed. This is a static file ready for the first release.
### 8. Generate .gitignore
Read `./references/gitignore-templates.md` for the curated language templates.
If a `.gitignore` already exists (e.g., generated by GitHub), merge the appropriate template entries into it, avoiding duplicates.
If no `.gitignore` exists, create one using the appropriate template based on the project type.
#### GitHub Fallback for Unlisted Types
When the user explicitly specifies a project type that is NOT in the curated list above:
1. Attempt to fetch the template from GitHub's gitignore repository using WebFetch:
```text
https://raw.githubusercontent.com/github/gitignore/main/{TemplateName}.gitignore
```
Derive `{TemplateName}` from the user-specified language using these candidates, tried in order until one succeeds:
- Title-cased with spaces removed (e.g., `visual studio` → `VisualStudio`)
- Title-cased with spaces replaced by `-` (e.g., `objective c` → `Objective-C`)
- The user's input as-is (e.g., `C++`)
URL-encode special characters in the URL (e.g., `C++` → `C%2B%2B`). Stop at the first successful (non-404) response.
1. **If any fetch succeeds**: merge the fetched entries with the common entries (`.DS_Store`, `.env`, `.claude/settings.local.json`), avoiding duplicates. Use the combined result as the `.gitignore`.
1. **If all candidate fetches fail** (404 or network error): fall back to the Generic template and inform the user that no template was found for that language.
This fallback is ONLY used when the user explicitly specifies a type not in the curated list. It is never used during auto-detection from an existing `.gitignore`.
### 9. Bootstrap Agent Config Files
Set up the hub-and-spoke agent configuration pattern (see the clean-up-agent-config skill for the full rationale). Create these files:
#### AGENTS.md
Read `./references/agents-md.md` for the AGENTS.md template and create the canonical instruction file from it.
- Replace the heading with the exact binary or repository name (kebab-case)
- Insert the short description in the Overview section
#### CLAUDE.md (symlink)
```bash
ln -sfn AGENTS.md CLAUDE.md
```
#### .claude/settings.json
Create a minimal team-shared settings scaffold:
```json
{
"$schema": "https://json.schemastore.org/claude-code-settings.json",
"permissions": {
"allow": [],
"deny": []
}
}
```
#### .github/copilot-instructions.md
Read `./references/copilot-instructions.md` for the Copilot instructions template and create a `.github/copilot-instructions.md` file from it.
- Replace the heading with the exact binary or repository name (kebab-case)
- The file cross-references AGENTS.md for full project conventions
### 10. Create docs/plans/
Use the Write tool to create empty `.gitkeep` files in both subdirectories:
- `docs/plans/todo/.gitkeep`
- `docs/plans/done/.gitkeep`
The Write tool creates parent directories automatically. The `todo/` subdirectory holds active plans; `done/` holds completed plans preserved for reference.
### 11. Create Initial Commit
Stage all generated files and create the initial commit:
```bash
git add -A
git commit -S -m "feat: scaffold new repository"
```
### 12. Summary
Print a summary of what was created:
- List every file generated
- Note the project type used for `.gitignore`
- Note the agent config files and symlink
- Suggest running the add-community-files skill to add CONTRIBUTING.md, CODE_OF_CONDUCT.md, .github/SECURITY.md, and .github/PULL_REQUEST_TEMPLATE.md
## Error Handling
- If the target directory already contains a `LICENSE` or `README.md`, ask the user before overwriting
- If a `.gitignore` already exists, merge new entries rather than overwriting
- If `git init` fails, continue generating files but warn the user
- If the user provides an unrecognized project type, attempt the GitHub fallback (see Step 8). If that also fails, fall back to Generic and mention it
## Reference Templates
- `./references/license.md` -- MIT license template
- `./references/readme.md` -- README template
- `./references/changelog.md` -- CHANGELOG template (Keep a Changelog format)
- `./references/gitignore-templates.md` -- Per-language `.gitignore` templates
- `./references/agents-md.md` -- AGENTS.md template
- `./references/copilot-instructions.md` -- `.github/copilot-instructions.md` template
---
> Source: [cboone/agent-harness-plugins](https://github.com/cboone/agent-harness-plugins) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->
章节与文件索引
按说明文件中的顺序排列。
1. 收集项目信息
2. 检测用户身份
3. 准备目录
4.初始化Git
5. 生成许可证
文件/命令 -> go-cli · go-library · javascript · pascal · python · ruby · rust · shell
内容校验值 -> ba8242769c10
当前原文的自动摘译,尚未人工审校。
1. 收集项目信息
如果用户在请求中提供了项目名称,请直接使用它,而不是从 git remote 或 README 中检测。如果他们指定了项目类型(
go-cli、go-library、javascript、pascal、python、ruby、rust、shell、swift、zig-cli之一,generic),使用它而不是从.gitignore推断。任何剩余参数仍应正常收集。自动导出您可以导出的内容,然后仅询问缺少的内容:2. 检测用户身份
检测用户的 GitHub 用户名和全名以在模板中使用:如果任一命令失败或返回空输出,请要求用户提供值。在模板引用
GITHUB-USERNAME的地方使用 GitHub 用户名,在引用COPYRIGHT-HOLDER的地方使用全名。3. 准备目录
如果当前目录为空或用户指定了目录名称:如果当前目录已有文件,请在将样板与现有内容一起添加之前与用户确认。
4.初始化Git
如果已经在 git 存储库中,则跳过。
5. 生成许可证
阅读 MIT 许可证模板的
./references/license.md并从中创建一个LICENSE文件。将YEAR替换为当前年份(运行date +%Y以获取它)将COPYRIGHT-HOLDER替换为检测到的全名