本文へ移動
cccskills
無料GitHub で公開

cxc-dev

Use for coding, PR delivery, scaffolding and QA. Triggers: develop, fix, refactor, test, review, docs, browse, stacked PR, 개발, 수정, 검토, 스택 PR.

インストール方法を見る

含まれるファイル(18)

  • SKILL.md11.9 KB
  • agents/openai.yaml143 B
  • references/async-questions.md6.0 KB
  • references/browser-routing.md3.4 KB
  • references/code-mode-examples.md4.3 KB
  • references/development-practice.md6.3 KB
  • references/hosted-ci-evidence.md3.2 KB
  • references/logging.md2.8 KB
  • references/methodology-overlays.md2.8 KB
  • references/native-execution.md6.3 KB
  • references/peer-collaboration.md10.6 KB
  • references/product/crud-product-development.md2.7 KB
  • references/reader-documents.md6.7 KB
  • references/skill-catalog.md14.1 KB
  • references/skill-ownership.md5.0 KB
  • references/stacked-prs.md16.0 KB
  • references/static-analysis-gate.md2.6 KB
  • references/static-analysis.md3.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Dev

User/host safety and tool contracts prevail. Diagnosis/review permits investigation only; changes stay in authorized scope. Prose is not runtime enforcement.

§0.0 Work Classifier (C0-C5)

DEV-CLASS-01 (DEFAULT): classify before depth; reclassify growth. Decide discovery ownership before broad reads, even read-only.

ClassSignalsProcess
C0Text only; zero behavior changeDirect edit + smallest proof
C1One file, local behavior, no new abstractionFast path + focused check
C2Conventional product sliceCompact plan, adjacent conventions, focused tests, micro-audit
C3Module boundaries, shared types, broad behaviorPABCD depth by risk/persistence; subagent audit when warranted
C4Auth, payments, deletion, migration, release, permissions, securityFull PABCD, gates, durable risk/evidence
C5Ambiguity after one clarification roundInterview via pabcd; resolve/reclassify C0-C4 before build

Tie-break: higher class wins (DEFAULT); route→service→storage remains C2. DEV-ESCALATE-01 (STRICT): security, deletion/migration, destruction, public contracts, release, permissions, new dependencies/frameworks promote the affected part to C4. Split it out; promotion alone requires no question.

§0.1 Patch Fast-Path (C0/C1)

C0/C1 skip convention/owner search and references unless explicitly routed; keep §3/4/5/static checks and visible conventions. Five lines is illustrative. Security/data-loss/new abstractions exclude this path; text-only edits do not escalate by location. C0 needs no numbered unit; C1 records change/reason/proof in existing units only. Never create units just for C0/C1; unit residence owns UNIT-RESIDENCE-01.

§0.2 Rule Classes

Safety/correctness/permissions/truthful proof are mandatory. Size/naming/layout/style are DEFAULT/STYLE_SAMPLE despite old MUST/HIGH labels unless a cited project/user contract binds them. Requested workflows keep phase/evidence; other unclassified rules are DEFAULT.

  • STRICT: violation blocks completion.
  • DEFAULT: follow unless a stated, documented reason warrants deviation.
  • HEURISTIC: judgment guide; deviation needs no rationale.
  • DEV-STYLE-SAMPLE-01 (STYLE_SAMPLE): illustration, never universal.
  • ESCALATE: stop and ask the user.

§0.4 Workflow Modes

Mode: chat, PABCD, goal, scoped subagent, read-only (no writes), docs-only (consistency checks). Read pabcd/cxc-loop for mechanics; classify each work-phase. Docs-first: cxc-loop (LOOP-DOCS-FIRST-01). Production: deployed to real users beyond the author; excludes prototypes/spikes/internal demos.

Companion Skills

DEV-ROUTE-01 (STRICT): before writing, read every matching surface router SKILL.md; C0/C1 exceptions apply.

Reading contract

Read active SKILL.md fully; references only when applicable. Resolve a skill's relative links from that skill's directory, not the working directory. Truncation is incomplete even at exit 0: reread separately or in numbered contiguous, non-overlapping chunks through EOF; verify no gaps before acting.

Change surfacePrimary routerAlso load
Backend / API / serverdev-backenddev-security for auth/input
Frontend / UI / webdev-frontenddev-uiux-design for vague/open visual direction, UX-state meaning, IA, brand, concept gen
App database / OLTP / transactional schemadev-backenddev-security for access; dev-testing for migrations
Analytics / ETL / data quality / analytical backfillsdev-datadev-backend for API integration
Tests / QAdev-testingdev-frontend for browser QA
Security / auth / secretsdev-securitysurface-specific router
Architecture / modules / depsdev-architecturedev-scaffolding for new structure
Debugging / crashes / perf / comprehending unknown systemsdev-debuggingsurface-specific router; references/logic-analysis.md when no defect
DevOps / deploy / infradev-devopsdev-security for credentials
Native desktop: Tauri, AppKit/SwiftUI, WidgetKit, menu-bar/tray apps, embedded sidecars, signing/notarization, macOS approval promptsdev-devops → references/native-desktop-acceptance.md and references/macos-system-approvals.mddev-testing for suites and CI matrix; cxc-qa for gui/cli verdicts; dev-frontend for web-view UI; dev-security for entitlements and credentials; dev-debugging runtimes/swift.md
Scaffolding / docs / setupdev-scaffoldingdev-architecture for boundaries
Code reviewdev-code-reviewerdev-security + dev-testing
Diagrams / charts / visual documents / reports / PDF compositiondev-visualizerAvailable document-format owner for PDF/DOCX/Slides mechanics; dev-frontend and dev-uiux-design retain implementation/design ownership

Subagent Skill Injection (DEV-SKILL-INJECT-01)

Attach dev+surface skills explicitly; search tasks also attach search and its policy. Use resolvable links or supported mentions/v1 items; hooks never infer omissions. Mappings: ownership; triggers: agents/openai.yaml.

Discovery delegation

Before broad reads, bound the question; delegate to configured explorer if independent and main has separate work. State scopes; host/no-delegation limits win. Record unavailability; read narrowly. Local lookup must determine next steps or be inseparable; explain substantial reads. Read-only/counts/parallelism do not justify them. Revisit on new subsystems/rereads/truncation; reclassify growth. Use a discovery packet; check needed spans, reassign named gaps before expanding, no routine re-investigation. Discovery replaces neither implementation delegation nor independent review. Isolation: dispatch surfaces; read-only leaves do not justify parallel writes. Authorized delegation needs no new approval. Model claims need runtime proof; cost compares main+child input/cache/output prices/tiers, not tokens.

Family Invariants

  • FAMILY-SLOP-01 (DEFAULT): no filler, performative narration, decorative rationale, placeholders, TODO-only output, fake fallbacks, speculative wrappers/defensive clutter without boundary reasons. Prose/page tells: kwrite and dev-visualizer REPORT-DESIGN-01.
  • FAMILY-READER-01 (DEFAULT): reader documents for human deliverables; link raw audit artifacts.
  • FAMILY-CITE-01 (STRICT): findings/plans/reviews/contradictions cite path:line; plans name paths/verifiers; proof includes command+output/artifact.
  • FAMILY-PROOF-01 (STRICT): completion follows §3; all routers inherit it.

3. Verification Before Completion (STRICT)

  1. Identify the command proving the claim.
  2. Run it fresh, never cached.
  3. Read full output; check exit code and count failures.
  4. Confirm it supports the claim.
  5. Report the claim with evidence.
ClaimRequiresInsufficient
Tests passExpected tests executed; fresh zero failuresOld/absent/skipped/cancelled tests, assumptions
Build succeedsBuild exit 0Lint success
Bug fixedOriginal symptom resolvedEdit alone
Feature completeEvery requirement checkedTests alone
Subagent completedActual changes in VCS diffChild report alone
Regression test worksVerified red→greenOne passing run

DEV-VERIFY-FLOOR-01 (STRICT): floor, not cap:

ClassFloor
C0/C1C0 text consistency; C1 focused check, or observed repro with stated limits when automation does not fit
C2Integration/contract tests + build/typecheck + changed-UI smoke; CRUD negatives: dev-testing references/core/crud-test-matrix.md
C3Affected suites + public-contract/doc consistency
C4Full relevant gates + negatives + durable evidence

Verify child success independently: diff and behavior.

4. Change Documentation

C2+ supplied logs record change/reason/proof. C0/C1 follow §0.1; discovered logs create no duty. Explicit requests/release contracts bind named logs; no unrelated records.

5. Safety Rules

  • Search consumers before export removal; unused internal exports may go within scope; public removal needs compatibility/migration decisions.
  • Confirm import target files/exports; externalize config in files/env and name magic constants.
  • Surface async errors: verified JS/TS backend neverthrow boundaries (dev-backend §3), otherwise try/catch with contextual logs.
  • Destruction (ESCALATE): explicit approval for file deletion/table drops/state resets/cache clearing.
  • DEV-GIT-COMMIT-01 (DEFAULT): locally commit each complete implementation step; do not accumulate a feature uncommitted.
  • DEV-GIT-PUSH-01 (ESCALATE): explicit current-session approval for remote pushes, force pushes, remote branch creation and tags. Local commits are autonomous; completion grants no push permission.
  • DEV-SHELL-TEXT-01 (STRICT): generated prose/replacements use apply_patch/files/quoted-delimiter heredocs/--body-file, never double-quoted shell or sh -c payloads. Use git -C <source>; hooks cannot see workdir. SHELL-SUBST-01/WORKTREE-GUARD-04 are narrow safeguards.
  • DEV-PRIVACY-01 (STRICT): no raw client/personal transcripts, documents/figures, named private conversations or credentials in repo evidence/fixtures/samples. Store outside checkout; devlog records filename/date/summary. Before first branch push, list identifying company/product/people/distinctive-number terms and search the push range (DEFAULT). Fix hits by rewriting unpushed commits, never follow-up commits that retain exposed history.
  • Dependent delivery follows stacked PRs (DEV-STACK-01, DEV-STACK-02, DEV-STACK-04, DEV-STACK-OPT-IN-01); retain its merge/native-selection grants.

Conditional Routes

Read matching rows; repo tools own local facts.

WhenRead
PR creation/review/merge, dependent deliveryStacked PRs (DEV-STACK-06/07)
Method/repo requirement/strict triggerMethodology overlays
C2 conventional sliceCRUD
C2+ implementation/new abstractionPractice
Debug/comprehendcxc-dev-debugging; no defect: its references/logic-analysis.md
Hosted CICI evidence (DEV-CI-EVIDENCE-01)
QuestionsAsync questions
Peer contactDefault-off; peer collaboration
Composition/projection/JSNative execution
Browser proof/extraction/UI QABrowser routing
Library behaviorContext7 resolve-library-id → query-docs; otherwise official docs
Current/public/HTTP evidencecxc-search
Lost prior contextDEV-RECALL-01 (STRICT): cxc-recall chat+memory search; both miss: ask/report searches
Code smellscxc-dev-code-reviewer §3; boundary errors: dev-architecture §4
Types/static checksStatic analysis, gates
Lane observationWaiting (DISPATCH-POLL-BUDGET-01)
Capability gapInstalled skills come from the host's skill list and these routers. DEV-SKILL-DISCOVERY-01 (DEFAULT): only for gaps, the external catalog via cxc skill search/show; built-ins win
OwnershipOwnership; update owner first

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use for AST search and codemods. Triggers: ast-grep, sg, function/call/class/import, empty catch, missing await, YAML rules.

日本語の概要は準備中です。原文の説明を表示しています。

lidge-jun/codexclaw452026年10月9日 更新

Use for module boundaries and dependencies. Triggers: circular import, coupling, barrel, re-export, validation placement, 모듈 경계, 순환 참조.

日本語の概要は準備中です。原文の説明を表示しています。

lidge-jun/codexclaw452026年10月9日 更新

Use for APIs, servers and app databases. Triggers: REST, GraphQL, migration, query optimization, middleware, caching, queues, 백엔드, API 작업, 마이그레이션, 쿼리 최적화.

日本語の概要は準備中です。原文の説明を表示しています。

lidge-jun/codexclaw452026年10月9日 更新

Use for code/PR/diff review and refactor audits. Triggers: review this, before merge, antipattern, 리뷰, 코드 리뷰, 머지 전에 확인.

日本語の概要は準備中です。原文の説明を表示しています。

lidge-jun/codexclaw452026年10月9日 更新

Use for analytics and data pipelines. Triggers: ETL, ELT, data quality, SQL optimization, schema drift, backfill, 데이터 파이프라인, 데이터 품질, 백필.

日本語の概要は準備中です。原文の説明を表示しています。

lidge-jun/codexclaw452026年10月9日 更新

Use for debugging and system comprehension. Triggers: debug this, root cause, how does X work, reverse engineer, 왜 안 돼, 디버깅, 원인 분석, 로직 파악, 뜯어봐.

日本語の概要は準備中です。原文の説明を表示しています。

lidge-jun/codexclaw452026年10月9日 更新

lidge-jun のスキルをすべて見る

このスキルの問題を報告する