agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/devsquad-copilot/.github/plugins/devsquad/skills/init-scaffold/SKILL.md

init-scaffold

Skill50 starsChanged 16 days agoMITView on GitHub

Verify and create community and governance files (SECURITY.md, CONTRIBUTING.md, LICENSE, CODE_OF_CONDUCT.md). Use when initializing a project and the user wants to set up community files. Do not use for SDD Framework configuration files (use init-config) or documentation templates (use init-docs).

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When verifying status, for each file:

    line 21
  2. Distinctive:

    Check if the file exists at the repository root

    line 23
  3. Distinctive:

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

    line 30
  4. Very specific:

    Skip / Undecided: Use the placeholder from docs/templates/LICENSE.

    line 62
  5. Very specific:

    If Contributor Covenant: Generate the standard Contributor Covenant v2.1 text with the enforcement contact.

    line 70
  6. Very specific:

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

    line 71
  7. Very specific:

    When asked to create with --placeholder flag, skip all questions and create files directly from the templates in docs/templates/, …

    line 75
  8. Distinctive:

    All files are created at the repository root:

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Init Scaffold

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

FilePurpose
SECURITY.mdSecurity vulnerability reporting policy
CONTRIBUTING.mdContribution guidelines for collaborators
LICENSEProject license declaration
CODE_OF_CONDUCT.mdExpected behavior standards

These files are optional.

Verification Mode

When verifying status, for each file:

  1. Check if the file exists at the repository root
  2. 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:

  1. "Who should security vulnerabilities be reported to? (email, team alias, or link)"
  2. "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:

  1. "What is the project name?"
  2. "What is the branch naming convention? (e.g., feature/description, fix/description)"
  3. "What commit message convention do you use? (e.g., Conventional Commits, free-form)"
  4. "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:

  1. "Which license would you like? Common options: MIT, Apache 2.0, GPLv3, BSD, or proprietary/all rights reserved."
  2. "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:

  1. "Would you like to adopt the Contributor Covenant (widely used standard), or create a custom code of conduct?"
  2. "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.

File Placement

All files are created at the repository root:

  • SECURITY.md
  • CONTRIBUTING.md
  • LICENSE
  • CODE_OF_CONDUCT.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free