'contributing' 검색 결과

기술 문서와 에이전트·기여자용 지침 파일을 작성하고 검토합니다. 설명과 운영 절차, 다국어 버전의 일관성을 확인하고 근거가 충분한 문제를 수정합니다.

• 기술 문서 작성 및 갱신
• README와 문서 변경 사항 검토
• 에이전트 지침과 기여 절차 정리

Keep repository contribution guidance consistent after workflow changes. Compare agent skills, coding guidance, contributor documentation, and issue and pull request templates, then fix contradictory instructions, outdated references, and mismatched inventories.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check guidance after adding or renaming skills
• Align issue and pull request conventions
• Find outdated workflow references

Create and review technical documentation alongside repository instructions for agents and contributors. The skill checks clarity, working procedures, documentation coverage, and consistency across languages, then provides updated drafts or findings with validation notes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating or updating technical documentation
• Reviewing README files and documentation changes
• Aligning agent instructions with contribution procedures

Prepare and open a pull request for an external contribution to prisma/orm. Check contribution rules, change scope, tests, and contributor signoffs, then draft the title and explanation for approval before submitting from a fork.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Submitting a Prisma contribution from a fork
• Checking tests and scope before requesting review
• Verifying contributor signoffs on every commit

Check a local Codewhale checkout before contributing: inspect branch and sync status, build the CLI, and run the repository’s CI checks. Present recent commits and changelog entries from local files, with clear status for each step.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking a checkout before contributing
• Reviewing local changes and sync status
• Running the build and CI verification commands

Prepare repository contributions by checking existing guidelines, related issues, branch naming rules, commit formats, and pull request templates. Organize changes into logical commits and assemble submissions that follow the project's documented contribution process.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing issues using repository templates
• Creating branches with the required naming format
• Grouping changes into clear commits

Create a structured review after a production incident, focusing on systems and processes without blaming individuals. Reconstruct events, quantify impact, investigate causes, and document specific follow-up actions with named owners and deadlines.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Write a review after a production outage
• Reconstruct an incident timeline from records
• Separate root causes from contributing factors

Navigate Apache Beam contributions from finding an issue to submitting a pull request, a proposed code change, and responding to reviews. Covers environment setup, tests, formatting, licensing requirements, and closer evaluation of changes to core components.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a first Apache Beam contribution
• Organize a pull request and its related issue
• Check tests and formatting before submission

Write a CONTRIBUTING guide that helps people contribute to an open-source project without friction. Use when asked to write a CONTRIBUTING.md, set up contribution guidelines, or make a repo welcoming to contributors. Produces a clear guide: how to set up, the contribution workflow, standards, PR expectations, and how to get help — lowering the barrier to a first PR.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when contributing to Tel-Agent - picking an issue to work on, setting up the repository for the first time, starting or finishing a task, opening a pull request, or asking "what can I work on" / "how do I start" / "is my change ready to submit". Covers the full path from a fresh clone to a merged pull request.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Contribute documentation improvements to an OSS repo. Identifies doc gaps, studies the docs system, and verifies accuracy against source code. Use when contributing documentation to an open source project, fixing outdated setup instructions, adding missing API docs, or improving README clarity. Not for writing docs for your own project — this is for contributing docs to someone else's repo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Regenerate the translations POT file after modifying English user-facing documentation. Use when docs/src/**/*.md files outside contributing/ are changed. Skip when only docs/src/contributing/** changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when taking a repo open source, or hardening one that already is. Run /oss-launch and it scans the repo (stack, existing files, git remote, secrets), asks only what it cannot infer, then generates a tailored OSS file collection (README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, CHANGELOG, .gitignore, .github/ issue + PR templates, CI/CD). Also covers launch (GitHub metadata, badges, Show HN, Reddit, YouTube), release cadence (SemVer + CHANGELOG), and demo-GIF generation. Triggers on "open source this", "OSS checklist", "prep for launch", "make this repo public", "add a license / contributing / security policy", "Show HN", "release workflow", "star growth", "get contributors".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive workflow for contributing features to open-source IDE and coding tool projects

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide for contributing to the tinker-cookbook repo — development setup, code style, type checking, PR process, and design conventions. Use when the user asks about how to contribute, set up the dev environment, code style, or project conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

REA 조사 도구를 설계하거나 변경할 때 담당 범위, 입출력, CLI 및 MCP 호출 규칙을 정리합니다. 조사 근거의 의미와 검증 방법을 포함한 설계안을 작성합니다.

• 새로운 REA 조사 도구 설계
• CLI 및 MCP 입출력 검토
• provider 책임과 Evidence 의미 정리

Compare release changes with project documentation, then update files such as README and CHANGELOG to reflect what shipped. The skill also checks architecture diagrams, maps missing documentation, and records remaining documentation work in the pull request.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Updating project documentation after a release
• Checking architecture diagrams against shipped changes
• Polishing changelog entries and organizing TODOs

Prepare Paperclip changes for a pull request by organizing commits, updating the branch, writing the description, addressing automated review feedback, and checking tests and CI before reporting the result for handoff.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing completed Paperclip changes for review
• Resolving Greptile feedback and failed checks
• Splitting large changes into separate pull requests

Create an HTML presentation diagnosing margin recovery for a regional grocery chain. Organize the central recommendation, contributing factors, priorities, and roadmap into a decision deck, using a coordinated sage, cream, and burnt-orange visual style.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Presenting a grocery chain's margin-recovery diagnosis
• Explaining initiative priorities to a steering committee
• Creating an advisory deck with a warm visual style

Review Archify issues, pull requests, and code by weighing user value, implementation and maintenance costs, and wider impact. Use evidence to decide whether work is worthwhile, compare alternatives, and identify questions that still affect the decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prioritizing reported issues
• Reviewing the cost and impact of a pull request
• Assessing code maintainability

Find and install reusable blocks and effects for HyperFrames, then connect them to an existing composition with timing and layer settings. The skill also guides creating, validating, and contributing new blocks or components.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add a reusable chart block to a video
• Merge a grain overlay into an existing composition
• Adjust block timing and layer order

Create integration tests for syncable metadata entities in Twenty itself. Cover invalid inputs, validation errors, and successful data operations, using reusable GraphQL request helpers, error snapshots, and cleanup routines to organize the test suite.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add integration tests for a new syncable entity
• Test required fields, duplicates, and invalid references
• Verify successful creation, updates, and deletion

Implement validation and migration action builders for syncable entities, data types handled by Twenty's synchronization system. This skill covers required fields, uniqueness, reference checks, and orchestration wiring, with validators that return errors without throwing exceptions or changing data.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add required-field and duplicate checks
• Validate references to parent entities
• Build create, update, and delete migration actions

Define the types and shared registrations needed to add a syncable entity to Twenty's server. Set up database entities, editable fields, action types, and relationships as the foundation for workspace migration implementation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Define a new syncable entity in Twenty
• Create flat data and migration action types
• Register editable fields and comparison rules