스킬 찾기

Update Flask-AppBuilder in Apache Airflow’s FAB provider, including pinned versions, dependency locks, and documentation. Check compatibility tests and review copied security code, with asset and database migration updates when the upstream release requires them.

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

• Upgrade the FAB provider to a newer Flask-AppBuilder release
• Review upstream authentication fixes against Airflow's copied code
• Resolve compatibility failures after a dependency update

Turn Airflow Improvement Proposals into practical guides checked against current code, or proposed user stories for design review before implementation. Organize use cases, distinguish verified examples from speculative code, and capture specific design questions.

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

• Create implementation-backed guides for an Airflow proposal
• Explore user stories before a feature is implemented
• Separate implemented features from proposed functionality

Guides contributors through adding a new programming language to Airflow, covering SDK structure, runtime coordination, communication rules, executable packaging, tests, and the documentation and configuration changes needed for a pull request.

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

• Adding support for a new programming language
• Choosing how Airflow launches a language runtime
• Implementing communication and executable bundles

Assess Airflow Improvement Proposals by comparing Confluence specifications with pull requests, commits, and codebase files. Produce evidence-backed progress reports showing delivered items, remaining work, and specification updates needed across one or more proposals.

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

• Check implementation progress for an Airflow proposal
• Compare specification deliverables with shipped code
• Compile a progress report across multiple proposals

Helps add or update translations for the Apache Airflow interface. Covers language setup, translation file generation, consistent terminology, preserved variables and plural forms, and checks for missing, unfinished, or unused entries.

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

• Adding a new interface language to Airflow
• Filling gaps in an existing translation
• Aligning terminology and preserving translation variables

Draft commit messages, pull request titles and descriptions, and GitHub comments or reviews for Apache Airflow contributions. Follows project wording and AI attribution rules, and helps decide whether a change needs a release note.

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

• Draft commit messages and pull request titles
• Prepare pull request descriptions using the project template
• Draft GitHub comments and review text

Guides preparation and authorized publication of Apache Airflow changes, including existing pull request checks, remote verification, reviews, tests, rebasing, and a prefilled submission page. Also explains how to track work deferred by temporary fixes.

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

• Planning the steps for submitting Airflow changes
• Checking existing pull requests and Git remote destinations
• Reviewing and testing changes before pushing

Write and review SQL for reports and metrics in a data warehouse, a store of analytical data. Applies rules for explicit columns, date filters, aggregate names, and limited exploratory results, returning SQL with a brief explanation.

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

• Write SQL for report and dashboard metrics
• Calculate counts, sums, and rolling metrics
• Combine data from multiple tables

Helps contributors develop and fix Airflow’s Java SDK for JVM tasks. Explains public API boundaries, JAR packaging, Python coordination, communication schema updates, and the test commands used to validate changes.

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

• Adding features or fixing bugs in the Java SDK
• Reviewing public API and internal implementation boundaries
• Investigating JAR discovery and JVM startup failures

Prepare Apache Airflow provider releases by classifying pending changes, inspecting pull request diffs for compatibility risks, and applying version bumps and changelog entries. Use existing breeze tooling to regenerate release documentation and consult the release manager on uncertain decisions.

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

• Prepare documentation for a regular provider release cycle
• Classify changes for a selected set of providers
• Review breaking changes and choose version bumps

Create or improve unit tests for Apache ShardingSphere classes. Cover the target class’s behavior and affected branches, verify explicitly requested coverage goals, and consolidate suitable scenarios into parameterized tests, which run the same checks with different inputs.

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

• Add missing unit tests for a target class
• Verify an explicitly requested coverage target
• Consolidate suitable tests with different input data

Review Apache ShardingSphere pull requests or authorized downstream changes using repository evidence. Assess code correctness, merge readiness, or CI failures, then produce consolidated findings or a ready-to-copy reply to a review discussion.

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

• Review code changes for correctness and regression risks
• Assess whether a pull request is ready to merge
• Investigate CI failures

Apply Apache ShardingSphere’s written coding standards during implementation or review, covering naming, Java constructs, tests, and Maven dependencies. Also audit a specified scope without editing files, combining automated checks with manual inspection of applicable rules.

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

• Check changed code against written repository standards
• Review Java naming and declaration conventions
• Verify changed Maven dependency declarations

Investigate Apache ShardingSphere issues using official documentation, code, tests, and issue discussions. Distinguish bugs, unsupported usage, duplicates, and enhancement requests, then draft a concise maintainer-style reply explaining the evidence and next action.

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

• Distinguish bugs from unsupported configurations
• Check whether an issue duplicates an earlier report or fix
• Draft a GitHub issue reply with clear next steps

Implement, fix, refactor, or remove repository code through a defined workflow. It connects each change to an acceptance criterion, checks effects on existing behavior, and guides focused testing, change review, and verification.

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

• Implementing a feature within an agreed scope
• Fixing bugs while preserving existing behavior
• Checking impacts before removing code

Prepare an Apache bRPC release with tracked progress, version updates, release candidate checks, and draft release notes and emails. The workflow leaves signing, publishing, and other external release actions to the release manager.

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

• Prepare version files and a release branch
• Resume release work from a saved progress record
• Verify local or uploaded release packages

Format C++ code in the BE and Cloud modules using the project's clang-format v16 rules. Use the provided scripts to fix formatting or check for violations without changing files, then review the resulting differences before committing.

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

• Format BE or Cloud C++ code before committing
• Fix formatting failures reported by CI
• Check formatting without modifying files

Review Doris code changes using project-specific checklists for data correctness, concurrency, memory safety, compatibility, performance, and tests. Trace related code paths and explain findings with concrete failure scenarios, using query plan trees when reviewing optimizer behavior.

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

• Review newly completed Doris code changes
• Check concurrency and memory management in related code paths
• Assess compatibility and test coverage before merging

Run clang-tidy static analysis, which checks code without executing it, on added or modified BE and Cloud C++ files. Focus diagnostics on changed lines, investigate bug, performance, and readability warnings, and verify fixes with another check.

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

• Check changed C++ code before committing
• Investigate clang-tidy warnings reported by CI
• Review changes against a specific branch

Diagnoses and fixes Java style violations in the FE module using Checkstyle, a tool that checks coding rules. It interprets errors, applies the project's formatting and import restrictions, and reruns checks to verify fixes.

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

• Checking FE Java changes before committing
• Fixing build failures caused by Checkstyle violations
• Understanding project-specific style and import rules

Prepare a clean Doris package and run Docker regression tests, which check whether changes break existing behavior. Restore configuration and startup files from Git, build the test image, and investigate failures using configuration checks and runtime logs.

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

• Run Docker regression tests before submitting Doris changes
• Test without local configuration changes affecting results
• Investigate missing test suites or startup failures

Run TVM's TIRx compiler tests alongside tirx-kernels import and correctness checks. It verifies the local build, selects GPUs, runs parallel tests, saves full logs, and guides failure investigation and result reporting.

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

• Testing TIRx compiler and kernel changes
• Checking tirx-kernels imports and registry entries
• Running parallel tests across selected GPUs

Extend and audit TVM's T.ptx instruction table for GPU code generation. It guides instruction definitions, checks generated assembly with CUDA tools, and aligns comments and supported forms with a chosen PTX specification version.

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

• Adding PTX instructions or qualifiers to T.ptx
• Extending supported operand types
• Investigating ptxas certification failures

Run a quick first review of code changes with six specialist agents working in parallel. They check logic, input and output, shared state, resources, missing behavior, and API completeness, then combine duplicate findings into a report ranked by confidence.

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

• Running a quick first review of a patch
• Screening diffs to prioritize further investigation
• Checking for missing cleanup and handlers