$ ~/registry/skill/microsoft-github-plugins-devsquad-skills-init-scaffold

SKILL

init-scaffold

Name: init-scaffold
Author: microsoft

Verify and create standard community and governance files for new projects.

Stars

★ 36

Source

GitHub

Updated

2026-07-05

// securityLow risk

Prompt only, no code
Open source

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "init-scaffold" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/init-scaffold/SKILL.md
2. Save it as ~/.claude/skills/init-scaffold/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Initialize governance files for an open-source repo

Prompt

Please check whether this new project is missing community governance files and create complete SECURITY.md, CONTRIBUTING.md, LICENSE, and CODE_OF_CONDUCT.md suitable for a public GitHub open-source repository.

Expected

Creates or completes the four standard governance files with content appropriate for a public open-source project.

Add policy files for an internal company project

Prompt

Add community and governance files for this internal project. First verify the existing repository files, then create any missing SECURITY.md, CONTRIBUTING.md, LICENSE, and CODE_OF_CONDUCT.md using wording better suited to internal company collaboration.

Expected

Produces governance files tailored to internal collaboration and avoids unsuitable open-source community wording.

Audit and fix missing repository files

Prompt

Please audit the current repository's community governance files, list which ones already exist and which are missing, and automatically create any missing SECURITY.md, CONTRIBUTING.md, LICENSE, and CODE_OF_CONDUCT.md.

Expected

Provides an audit summary first, then adds missing files as a ready-to-commit initialization result.

// docs

Init Scaffold

Manage 4 optional community and governance files at the repository root:

File	Purpose
`SECURITY.md`	Security vulnerability reporting policy
`CONTRIBUTING.md`	Contribution guidelines for collaborators
`LICENSE`	Project license declaration
`CODE_OF_CONDUCT.md`	Expected behavior standards

These files are optional.

Verification Mode

When verifying status, for each file:

Check if the file exists at the repository root
Return the status:
- Exists: file found (do not compare against a template)
- Missing: file not found

Guided Creation Mode

When creating files, use the Socratic approach for each file:

SECURITY.md

Ask:

"Who should security vulnerabilities be reported to? (email, team alias, or link)"
"What is the expected response timeline? (e.g., acknowledge within 2 business days)"

Generate content based on the template at docs/templates/SECURITY.md, replacing [TODO] markers with the answers.

CONTRIBUTING.md

Ask:

"What is the project name?"
"What is the branch naming convention? (e.g., feature/description, fix/description)"
"What commit message convention do you use? (e.g., Conventional Commits, free-form)"
"How many reviewers are required for a PR?"

Generate content based on the template at docs/templates/CONTRIBUTING.md, replacing [TODO] markers with the answers.

LICENSE

Ask:

"Which license would you like? Common options: MIT, Apache 2.0, GPLv3, BSD, or proprietary/all rights reserved."
"What is the copyright holder name? (e.g., organization or individual name)"

Based on the chosen license:

MIT: Generate the full MIT License text with the copyright holder and current year.
Apache 2.0: Generate the full Apache License 2.0 text with the copyright holder and current year.
GPLv3: Generate the full GNU GPLv3 preamble with the copyright holder and current year.
BSD 2-Clause: Generate the full BSD 2-Clause text with the copyright holder and current year.
Proprietary: Generate a simple "All rights reserved" notice with the copyright holder and current year.
Skip / Undecided: Use the placeholder from docs/templates/LICENSE.

CODE_OF_CONDUCT.md

Ask:

"Would you like to adopt the Contributor Covenant (widely used standard), or create a custom code of conduct?"
"Who should violations be reported to? (email or contact link)"

If Contributor Covenant: Generate the standard Contributor Covenant v2.1 text with the enforcement contact. If custom: Generate content based on the template at docs/templates/CODE_OF_CONDUCT.md, replacing [TODO] markers with the answers.

Batch Mode

When asked to create with --placeholder flag, skip all questions and create files directly from the templates in docs/templates/, preserving the [TODO] markers.