Skip to content

ccoalm/ccl-skills / skills/skill-extraction-workflow

skill-extraction-workflow

Flagged

复盘 / 沉淀 / 总结经验 / 补进技能 / 技能缺陷 / 流程优化 / would other teammates hit this / will we forget next time / teamwide recurrence / extract skill / post-mortem / 深度 review·审计技能仓库 / 对标外部技能包找 gap(benchmark superpowers·gstack 等) / 核查全局安装点(~/.config/opencode 等)旧快照是否遮蔽本仓技能 / 本仓(ccl-skills 等共享技能仓)OpenCode 项目配置·命令治理 → turn reusable lessons into durable CCL skills.

FileKindSize
SKILL.mdskill md111.0 KB
agents/openai.yamlconfig257 B
references/analysis-parse-fix-test-challenge-replay.mdmarkdown1.5 KB
references/attention-budget-ratchet.mdmarkdown13.7 KB
references/attribution-verification.mdmarkdown4.4 KB
references/bootstrap-slim-c3-obligation-table.mdmarkdown8.0 KB
references/correction-routing-map.mdmarkdown3.7 KB
references/coverage-exhaustion-traps.mdmarkdown19.6 KB
references/description-authoring.mdmarkdown21.1 KB
references/dual-track-review-gate.mdmarkdown110.6 KB
references/eval-routing.mdmarkdown22.2 KB
references/evidence-card-template.mdmarkdown3.2 KB
references/example-domain-preselect.mdmarkdown4.6 KB
references/external-practice-controls.mdmarkdown45.5 KB
references/extraction-lifecycle-handoff.mdmarkdown6.9 KB
references/extraction-quickstart.mdmarkdown20.2 KB
references/firing-point-placement.mdmarkdown21.3 KB
references/harness-patterns-and-eval.mdmarkdown42.6 KB
references/incident-postmortem-extraction.mdmarkdown28.8 KB
references/l0-l1-l2-routing.mdmarkdown10.3 KB
references/online-skill-review.mdmarkdown6.7 KB
references/parallel-stack-references-pattern.mdmarkdown35.9 KB
references/r0-leakage-audit.mdmarkdown19.9 KB
references/recurring-anti-patterns-checklist.mdmarkdown34.4 KB
references/resume-paused-delivery.mdmarkdown3.0 KB
references/review-feedback-mining.mdmarkdown5.7 KB
references/review-finding-standards.mdmarkdown7.3 KB
references/review-rubric.mdmarkdown3.1 KB
references/rule-consolidation.mdmarkdown38.2 KB
references/skill-listing-budget.mdmarkdown1.7 KB
references/source-register.mdmarkdown1.0 MB
references/source-to-skill-extraction.mdmarkdown109.3 KB
references/two-source-extraction-pattern.mdmarkdown19.4 KB
references/uiux-judgment-extraction.mdmarkdown19.1 KB
references/uiux-routing-map.mdmarkdown5.8 KB
references/validation-and-landing.mdmarkdown46.9 KB
scripts/AGENTS.mdmarkdown635 B
scripts/check-ccl-skills.shexecutablescript100.7 KB
scripts/check-contract-anchors.shexecutablescript5.6 KB
scripts/check-evidence-card-leak.shexecutablescript26.1 KB
scripts/check-mr-target-freshness.shexecutablescript9.4 KB
scripts/check-size-budget.shexecutablescript36.0 KB
scripts/check-sync-pointers.shexecutablescript22.6 KB
scripts/check_review_evidence_present.pyexecutablescript4.6 KB
scripts/contract-anchors.tsvother3.8 KB
scripts/entrypoint_form_census.pyexecutablescript7.1 KB
scripts/eval-golden-trace.rbexecutablescript10.0 KB
scripts/eval-health.rbexecutablescript14.6 KB
scripts/eval-routing-bank.rbexecutablescript30.4 KB
scripts/eval-routing.rbexecutablescript9.2 KB
scripts/extraction_review_gate.shexecutablescript1.8 KB
scripts/gate_receipt.pyexecutablescript24.7 KB
scripts/generic-r0-leak-scan.shexecutablescript12.4 KB
scripts/governing-chain-diff.pyexecutablescript12.8 KB
scripts/impact-chain-gate.rbexecutablescript124.4 KB
scripts/obligation-ledger.pyscript107.0 KB
scripts/reference-access-census.shexecutablescript8.3 KB
scripts/register-firing-path-resolution.rbexecutablescript48.4 KB
scripts/shared_git_surface_gate.pyexecutablescript38.0 KB
scripts/skill-behavior-eval.pyexecutablescript39.3 KB
scripts/skill-paired-eval.pyexecutablescript76.9 KB
scripts/source-register-lifecycle.rbscript1.5 KB
scripts/source-register-pending-status.rbscript2.0 KB
scripts/test_ai_coding_implementation_gates.shexecutablescript85.2 KB
scripts/test_antipattern_grep_panel.shexecutablescript3.2 KB
scripts/test_body_compliance_grading.shexecutablescript21.0 KB
scripts/test_check_ccl_impact_chain_refscripts.shexecutablescript145.1 KB
scripts/test_check_ccl_r0_status.shexecutablescript4.2 KB
scripts/test_check_ccl_register_pending_exclusion.shexecutablescript7.4 KB
scripts/test_check_ccl_regressions.shexecutablescript14.3 KB
scripts/test_check_ccl_route_drift.shexecutablescript22.6 KB
scripts/test_check_ccl_size_budget.shexecutablescript59.5 KB
scripts/test_check_ccl_skill_catalog.shexecutablescript23.3 KB
scripts/test_check_ccl_source_register_lifecycle.shexecutablescript6.1 KB
scripts/test_check_contract_anchors.shexecutablescript7.4 KB
scripts/test_check_mr_target_freshness.shexecutablescript12.8 KB
scripts/test_check_review_evidence_present.shexecutablescript4.3 KB
scripts/test_check_sync_pointers.shexecutablescript32.5 KB
scripts/test_ci_checkout_ref_binding.shexecutablescript8.2 KB
scripts/test_controlled_escalation_pins.shexecutablescript7.7 KB
scripts/test_entrypoint_domain_scan_terms.shexecutablescript8.8 KB
scripts/test_entrypoint_form_census.shexecutablescript6.3 KB
scripts/test_eval_routing_bank_grader_diagnostics.shexecutablescript20.6 KB
scripts/test_eval_routing_bank_resolution.shexecutablescript15.3 KB
scripts/test_eval_routing_bank_surface_binding.shexecutablescript6.9 KB
scripts/test_eval_routing_prose_target.shexecutablescript3.7 KB
scripts/test_eval_runtime.pyexecutablescript43.3 KB
scripts/test_extraction_review_gate.shexecutablescript15.2 KB
scripts/test_frozen_case_sanctity.shexecutablescript6.9 KB
scripts/test_frozen_case_sanctity_selfproof.shexecutablescript4.6 KB
scripts/test_gate_receipt.shexecutablescript17.7 KB
scripts/test_generic_r0_leak_scan.shexecutablescript6.4 KB
scripts/test_git_identity_predicate_gate.shscript13.8 KB
scripts/test_governing_chain_diff.shexecutablescript15.1 KB
scripts/test_impact_chain_gate_dateless_host.shexecutablescript6.8 KB
scripts/test_impact_chain_gate_verdict_differential.shexecutablescript20.8 KB
scripts/test_impact_chain_round_attribution.shexecutablescript32.5 KB
scripts/test_impact_chain_self_adjudication.shexecutablescript31.4 KB
scripts/test_impact_chain_source_refuted.shexecutablescript14.7 KB
scripts/test_liveness_predicate_gate.shexecutablescript14.5 KB
scripts/test_locale_independent_gates.shexecutablescript13.0 KB
scripts/test_obligation_ledger.shexecutablescript94.9 KB
scripts/test_obligation_ledger_repo_audit.shexecutablescript2.7 KB
scripts/test_pinned_phrase_mutation_walk.shexecutablescript6.5 KB
scripts/test_reference_access_census.shexecutablescript17.3 KB
scripts/test_register_firing_path_resolution.shexecutablescript41.0 KB
scripts/test_register_firing_path_wiring.shexecutablescript29.9 KB
scripts/test_regression_runner_lanes.shexecutablescript4.5 KB
scripts/test_regression_runner_registration.shexecutablescript1.5 KB
scripts/test_routing_bank_integrity.shexecutablescript15.5 KB
scripts/test_routing_pointer_integrity.shexecutablescript18.9 KB
scripts/test_shared_git_surface_gate.shexecutablescript76.8 KB
scripts/test_skill_paired_eval.pyscript60.0 KB
scripts/test_teardown_guard_pins.shexecutablescript17.0 KB
scripts/test_uiux_delivery_contract.shexecutablescript118.6 KB
scripts/test_uiux_loading_budget.shexecutablescript15.4 KB
scripts/test_validate_skill_credential_cwd.shexecutablescript2.6 KB
scripts/test_validate_skill_cross_refs.shexecutablescript4.8 KB
scripts/test_validate_skill_root_depth.shexecutablescript2.5 KB
scripts/validate-skill.shexecutablescript10.5 KB

references/review-finding-standards.md

View on GitHub
# Review Finding Standards

Shared output standard for any code/plan/design review, regardless of who runs it (human, Claude, Codex, an external review wrapper) or which path produced it. Two things must mean the same across all reviewers, or review and dual-track convergence are theater: **how severity is calibrated** and **what makes a finding actionable rather than noise**.

This file does NOT teach what to look for — that craft is owned where it is operational (see Non-Goals). It standardizes only the finding's severity and shape.

## Severity Rubric

Calibrate by *consequence and reversibility*, not by how clever the bug is or how confident the reviewer feels. Definitions are behavioral, not domain-specific. This file sets what each level *means*; the accept / defer / convergence mechanics that decide whether a landing may proceed are owned by `dual-track-review-gate.md` — apply both together.

- **P0 — must block landing.** Security breach, data loss/exposure, irreversible destructive action, auth / permission / tenant bypass, money/quota error, or production outage. These stay P0 *even when a later mitigation exists* — the ability to rotate keys, restore a backup, refund, or re-run a job does NOT downgrade enduring harm (exposure already happened, trust/auditability already breached). A P0 clears only by an applied fix, rollback/removal of the change, or an explicit risk-owner exception (not a routine owner sign-off) that records mitigation plus a tracking item per `dual-track-review-gate.md`. "Mitigation + ticket" must never be a rubber stamp on a known catastrophic risk.
- **P1 — should block landing.** Serious correctness, reliability, regression, privacy, or user-trust failure with a *genuine* recovery path — defined narrowly as complete restoration with no external exposure, no tenant/user-trust breach, no lost auditability, no unrecoverable money/quota effect, and no required customer or security incident response. Clears by an applied fix or an explicit deferred acceptance recording reason + residual risk; it does not silently pass. If a failure meets the P0 categories above, it stays P0 — you cannot reclassify it P1 by asserting a recovery path.
- **P2 — worth fixing, not landing-blocking.** Localized bug, maintainability issue, confusing copy, weak-but-present test, minor edge case. May be deferred freely; track for the next pass.

Scale reconciliation: some gates add an optional **P3** tier for nits / informational notes — treat it as a non-blocking sub-tier of P2. Structured finding schemas that accept only `P0|P1|P2` (e.g. `code-review`) fold P3 into P2.

Same tiers, different input: the P0/P1/P2 blocking semantics here are the canonical definition, and they are reused for **test-case priority** in `test-artifact-management` (P0 = must pass before release, P2 = nice-to-have). The difference is only the *input* that picks the tier — a review finding's tier comes from the defect's consequence/reversibility (above); a test case's tier comes from scenario centrality (primary/security path → P0, edge → P1/P2). The tier meaning (P0 blocks shipping — "landing" for a finding, "release" for a test case — P2 does not) is identical, so the two never need separate definitions.

Notes:
- When unsure between two levels, state the failure path and let consequence decide; do not average to the middle.
- "Style / preference" with no failure path is not a finding at any level — see noise below.
- Evidence quality is not severity. If a claimed P0/P1 lacks a concrete failure path, require clarification or mark the review **inconclusive** — do NOT lower the severity just because the report is under-specified. An under-described auth bypass is an inconclusive-blocking escalation, not a quietly-downgraded P2.

## Finding Quality

Every finding must carry the first three; the fourth is required when it can be known:

1. **failure_path** — the concrete way it breaks or gets exploited, specific enough to reproduce or trace ("on duplicate callback the row is written twice"), not a category ("idempotency issue").
2. **impact** — who/what is harmed and how badly; this is what sets the severity above.
3. **evidence** — a code path, a violated invariant, a reachable precondition, a threat-model step, a prior-incident pattern, or a reproduction. A *clean reproduction is not required* — hard-to-reproduce classes (races, prompt-injection, auth edge cases, distributed flakiness, supply-chain) are legitimately evidenced by a reachable code path plus plausible exploitability. What is rejected is speculation with NO code-path, invariant, or threat-model basis.
4. **smallest_fix** — the smallest credible change that closes it (not a redesign). When the reviewer can prove the breakage but cannot safely prescribe the patch (security, concurrency, infra, product-policy), use `owner investigation required` instead. Missing fix guidance lowers actionability; it does not erase a proven finding.

Noise, to be rejected before it enters a review result:
- vague approval/disapproval ("LGTM", "looks risky") with no failure path;
- restating what the code does without naming a failure;
- pure speculation with no code-path, invariant, or threat-model basis (distinct from an evidence-backed risk that merely lacks a clean repro — that is a real finding, and an uncertain high-impact one routes to `inconclusive`/escalation, never to noise);
- scope-expansion suggestions ("while you're here, also rewrite X") unless they close a named failure;
- duplicate findings that restate one root cause as several.

**Validity contract (this file owns this; the gate owns the consequences).** A result is one of three states:
- *findings* — one or more entries each meeting the bar above;
- *no-findings* — a valid, strong result ONLY when accompanied by an inspection record: scope reviewed, files/diffs actually inspected, any checks/commands run, explicit limitations, and reviewer/tool attribution. An empty list with no inspection record is `inconclusive`, not "no findings";
- *inconclusive* — empty/partial/tail-only/timed-out/unparsable output, an unverified claimed-blocking finding, or a no-findings result lacking the inspection record.

`dual-track-review-gate.md` owns what each state does to a landing (block / accept / defer / rerun); this file owns what makes each state valid.

## Non-Goals (route, do not duplicate)

This file standardizes the *output* of a review (severity + finding shape + validity), not its *depth*. Output conformance is not review depth: a finding set that fits this shape but was produced by a shallow skim is still a weak review. So before applying this standard, **name the review lens** — pick the owner/checklist that matches the change's risk (the routes below); if none applies, state explicitly what lens you used to decide what to look for. Then do NOT grow this file into a bug taxonomy, security checklist, or test strategy — route those to their owners:

- which risk classes a change carries / which gates apply → `feature-risk-router`
- what tests miss, assertion strength, scenario coverage → `testing-strategy`
- adversarial / chaos failure modes and when two review passes are required → `dual-track-review-gate.md`
- stack-specific pitfalls → the per-stack dev skills
- CLI/tool invocation mechanics for a specific reviewer → e.g. `code-review`

If a candidate rule names specific bug classes, it belongs in one of those owners, not here.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall