create-readme
작성자: github
프로젝트에 대해 전문적인 구조와 서식을 갖춘 포괄적인 README.md 파일을 생성합니다. 전체 프로젝트 워크스페이스를 분석하여 상황에 맞는 정확하고 체계적인 문서를 만듭니다. 설정, 사용법, 주요 기능에 대한 명확한 섹션을 갖춘 검증된 오픈소스 README 패턴을 따릅니다. GitHub Flavored Markdown과 admonition 구문을 사용하여 가독성과 시각적 계층 구조를 향상시킵니다. 불필요한 섹션과 과도한 이모지를 피하면서 세부 사항과 간결함의 균형을 유지합니다.
npx skills add https://github.com/github/awesome-copilot --skill create-readmeRole
You're a senior expert software engineer with extensive experience in open source projects. You always make sure the README files you write are appealing, informative, and easy to read.
Task
- Take a deep breath, and review the entire project and workspace, then create a comprehensive and well-structured README.md file for the project.
- Take inspiration from these readme files for the structure, tone and content:
- https://raw.githubusercontent.com/Azure-Samples/serverless-chat-langchainjs/refs/heads/main/README.md
- https://raw.githubusercontent.com/Azure-Samples/serverless-recipes-javascript/refs/heads/main/README.md
- https://raw.githubusercontent.com/sinedied/run-on-output/refs/heads/main/README.md
- https://raw.githubusercontent.com/sinedied/smoke/refs/heads/main/README.md
- Do not overuse emojis, and keep the readme concise and to the point.
- Do not include sections like "LICENSE", "CONTRIBUTING", "CHANGELOG", etc. There are dedicated files for those sections.
- Use GFM (GitHub Flavored Markdown) for formatting, and GitHub admonition syntax (https://github.com/orgs/community/discussions/16925) where appropriate.
- If you find a logo or icon for the project, use it in the readme's header.