스킬 검색.../

Commit | Skills Pool

스킬 파일

Commit

Create a conventional commit for PX4 changes

PX411,537 스타2026. 4. 13.

직업: 컴퓨터 프로그래머
카테고리: 코드 품질

스킬 내용

PX4 Conventional Commit

Create a git commit: type(scope): description

NEVER add Co-Authored-By lines. No Claude attribution in commits.

Follow CONTRIBUTING.md for full project conventions.

Steps

Read CONTRIBUTING.md for commit message format, types, scopes, and conventions.
Check branch (git branch --show-current). If on main, create a feature branch. Use <username>/<description> format where <username> comes from gh api user --jq .login. If unavailable, just use <description>.
Run git status and git diff --staged. If nothing staged, ask what to stage.

관련 스킬

빠른 설치

Commit

npx skills add PX4/PX4-Autopilot

Skill 다운로드 저장소 열기

작성자: PX4
스타: 11,537
업데이트: 2026. 4. 13.
직업

이 페이지의 내용

01PX4 Conventional Commit 02

Follow the commit message convention from CONTRIBUTING.md: pick the correct type and scope, write a concise imperative description. The scope table is not exhaustive — derive the scope from the directory path of the changed files.

Body (if needed): explain why, not what.

Run make format or ./Tools/astyle/fix_code_style.sh <file> on changed C/C++ files before committing.

Check if GPG signing is available: git config --get user.signingkey. If set, use git commit -S -s. Otherwise, use git commit -s.

Stage and commit. No Co-Authored-By.

If the user provided arguments, use them as context: $ARGUMENTS

Steps

Openclaw Release Maintainer

Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.

Verify

Use when you want to validate changes before committing, or when you need to check all React contribution requirements.

Flow

Use when you need to run Flow type checking, or when seeing Flow type errors in React code.

자동화 도구

Fix

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

Hygiene

Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.

microsoft184.0k

Add Policy

Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

microsoft184.0k

컴퓨터 프로그래머