Skip to main content
GitHub リポジトリ

sc-lint

sc-lint には randlee から収集した 14 個の skills があり、リポジトリ単位の職業カバレッジとサイト内 skill 詳細ページを表示します。

収集済み skills
14
Stars
1
更新
2026-05-26
Forks
0
職業カバレッジ
3 件の職業カテゴリ · 100% 分類済み
リポジトリエクスプローラー

このリポジトリの skills

sc-lint-version-adoption
ソフトウェア開発者

Guide a consuming repository through `sc-lint-version` adoption using the authoritative consumer-integration workflow, existing CLI testability seams, existing simulators or transcripts, and only thin normalization hooks when unavoidable.

2026-05-26
codex-orchestration
ソフトウェア開発者

Orchestrate sc-lint sprint work where team-lead coordinates, clint is the sole developer, and quality-mgr enforces the QA gate.

2026-05-25
team-lead
ソフトウェア開発者

Session initialization for the team-lead identity. Confirms identity and detects whether a full team restore is needed. Only run when ATM_IDENTITY=team-lead.

2026-05-25
todo-triage
ソフトウェア品質保証アナリスト・テスター

Run the repo Rust TODO finder during sprint-end or integration review and turn every discovered TODO into a QA finding rather than deferred work.

2026-05-25
triaging-findings
ソフトウェア品質保証アナリスト・テスター

Orchestrate pre-dispatch QA finding triage as team-lead. Launch one qa-triage agent per finding, collect phase-scoped Turtle records, aggregate by promoted branch, and only then dispatch branch-scoped fix assignments to clint.

2026-05-25
plan-hardening
ソフトウェア開発者

Team-lead drives plan hardening after the current plan state already exists in repo docs.

2026-05-25
phase-orchestration
ソフトウェア開発者

Orchestrate multi-sprint phase execution as team-lead. Manages sprint waves, scrum-master lifecycle, PR merges, clint reviews, and integration branch strategy. This skill is for team-lead only, not for scrum-masters.

2026-05-10
quality-management-gh
ソフトウェア品質保証アナリスト・テスター

Reusable QA orchestration skill for GitHub PRs. Use for multi-pass QA, CI monitoring, and template-driven findings and final quality reports.

2026-05-10
creating-ai-clis
ソフトウェア開発者

Create or harden CLIs intended primarily for AI or system consumption and secondarily for humans. Use when designing or implementing a JSON-first CLI with an MCP-ready contract seam, where every command supports machine output, errors are typed and actionable, mutating commands are auditable via corresponding read commands, and external integrations need simulator-backed testing. Do not use for human-first shell utilities, one-off scripts, or text-only CLIs.

2026-05-09
designing-cli-simulators
ソフトウェア開発者

Design stateful simulators for AI-facing CLIs that integrate with devices, networks, services, or databases. Use when a CLI needs realistic simulator-backed testing, configurable fault injection, persistent state, and a swappable adapter boundary so the same business logic runs against live and simulated backends. Do not use for shallow mocks, stateless test doubles, or CLIs with no external integration.

2026-05-09
restore-team-communications
ソフトウェア開発者

Repair Claude teammate routing after same-session compaction or resume when sc-lint still exists on disk and the saved leadSessionId still matches the current SESSION_ID, but SendMessage or teammate reachability is broken.

2026-05-07
rust-best-practices
ソフトウェア開発者

Review Rust architecture plans, crate boundaries, and code for structural design-pattern compliance. Use when the task involves typestate, sealed traits, error contracts, wrapper/newtype design, object safety, interior mutability, or other type-system-driven Rust correctness patterns that go beyond general style guidance.

2026-05-07
rust-development
ソフトウェア開発者

Develop, review, and explore Rust code with strict adherence to Pragmatic Rust Guidelines. Use when the user mentions Rust, .rs files, Cargo, clippy, rustdoc, or requests Rust architecture, implementation, or review.

2026-05-07
sprint-report
プロジェクト管理専門家

Generate a sprint status report for the current phase. Default is --table.

2026-05-07