القائمة
Creates commits following project conventions. Handles Conventional Commits with project-specific scopes, PR title requirements, and CI validation rules.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Add a namespace/module to a @kitz package — including extending the @kitz/effect namespaces. Covers the _.ts/__.ts barrel pattern, the package exports map, and import conventions.
Audits the project for consistency issues that may arise from manual editing. Checks package scripts, tsconfig paths, README tables, and other conventions.
Authors and manages global package scripts using the _: prefix convention. Scripts defined in root package.json are propagated to all packages with the prefix stripped.
Create a new @kitz/<concept> package via the Vite+ generator. Scaffolds package.json (live-types exports + effect peer), the layered tsconfigs, and the namespace barrel, then wires it into the workspace.
Use when adding project conventions, coding rules, or guidelines. Determines correct location and scoping based on which packages the rule applies to.
Use when filing a GitHub issue for this repo — a bug found during QA/stress-testing, or a feature/enhancement request. Enforces the two permitted cold-startable formats (bug = Expected/Actual, feature = Current/Desired), point-form-only bodies, and the gh filing procedure. Trigger on "file an issue", "open a bug", "log this finding", "make a gh issue", or after stress-testing surfaces a defect.
| name | committing-changes |
| description | Creates commits following project conventions. Handles Conventional Commits with project-specific scopes, PR title requirements, and CI validation rules. |
git add<type>(<scope>): <description>Package name minus @kitz/ prefix. Comma-separate for multiple packages. Omit for repo-level.
feat(core): add new utility # @kitz/core
fix(core, arr): update shared type # Multiple packages
ci: add Vercel Remote Cache # Repo-level (no scope)
| Type | Description | Version Bump |
|---|---|---|
feat | New feature | Minor |
fix | Bug fix | Patch |
docs | Documentation | Patch |
perf | Performance improvement | Patch |
style | Formatting, whitespace | None |
refactor | Code change (no behavior change) | None |
test | Adding/updating tests | None |
build | Build system, dependencies | None |
ci | CI configuration | None |
chore | Other maintenance | None |
chore.docs | README, guides (not code docs) | None |
chore.docs vs docs:
docs(pkg): JSDoc, code comments → Patch release, full CIchore.docs: README, guides → No release, CI skippedCI Skips: ci: or chore.docs: PR titles skip code checks (only format runs)
Releases: Handled automatically by @kitz/release based on conventional commits. No manual steps required.
<!-- cc-bypass --> in PR body: Skip CC validationfeat = "new capability", fix = "works better"