@OutlineDriven
組織
Outline-Driven Development - methodology between vibes and specs. Plugins for Claude Code, Codex CLI, and Gemini CLI. AST tooling + context engineering.
300 スキル1 リポジトリ 38
Use when planning an end-to-end fuzzing program for a project: engine and target selection, corpus management, and CI or nightly wiring. Not for harness design: use fuzz-harness-writing. Not for engine operation or triage: use libfuzzer. Not for sanitizer flag reference: use sanitizers.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a LibAFL fuzzer needs an executor, observer, feedback, mutator, scheduler, or objective composed around a target. Not for remote, credential, publish, deploy, or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a redacted, trimmed agent transcript must be appended to a GitHub PR or issue body, with human approval and preview. Not for automated or model-initiated insertion.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a human explicitly asks to commit and push to the checked-out branch, including directly to the default branch, with no branch creation and no pull request. Not for a feature branch off the default: use commit-push-pr in its no-PR mode.
日本語の概要は準備中です。原文の説明を表示しています。
Use when finding duplicate GitHub issues or checking for similar issues against a target issue. Not for closing, labeling, or modifying any duplicate issue.
日本語の概要は準備中です。原文の説明を表示しています。
Use when enrolling a project in OSS-Fuzz, running its helper workflow locally, or reproducing an OSS-Fuzz report. Not for remote, credential, publish, deploy, or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to set up and run coverage-guided fuzzing of Ruby code or C extensions with Ruzzy, producing crash reports or clean campaign summaries. Not for C/C++ fuzzing: use libfuzzer or libfuzzer.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push-pr.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to create or update a PR, revise its description, or link issue references to its body. Not for multi-PR stacks: use gate-and-merge. Not for releases: use git-workflow-and-versioning.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementation is complete, the test suite is green, and an integration decision is needed for a development branch or worktree. Not for failing tests or starting new work.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to fix P0s, address critical issues, or work on priorities from the weekly product briefing. Don't use for non-P0 issues or local bug fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when landing a queue of open PRs: gate each PR, sweep its review feedback to root cause, then merge, repair, hold, or close it. Human-only.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to find PRs to review or check the team review queue. Not for summarizing or resolving feedback on a specific PR: use resolve. Read-only.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked for multi-commit stack edits, rebases, fixups, or stacked-PR publishing with branchless git idioms. Not for plain-git workflows in repos without branchless.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user explicitly invokes branch or worktree cleanup for a repo with accumulated local branches. Don't use for remote branch deletion or force-push operations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a repository needs Git safety controls: guard destructive commands, set up gitignore or fix gitignore when untracked files keep appearing, or install or repair a repository-local pre-commit hook from project gates, including package-manager-native commit-time checks. Not for remote, credential, publish, deploy, or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks about recent engineering work, what the team is working on, planning or roadmap material, or an explicitly requested Slack summary. Not for remote or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for release, version bump, changelog, or branch workflow beyond a single commit. Don't use for single commits or for publishing to a package registry.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a human asks to compare one closed or stale tracker issue with current reality and mark it done or update it. Don't use for bulk issue reconciliation or multi-issue sweeps.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a human invokes triage on a new configured Slack issue report. Not for triaging reports from other channels or posting more than one verdict.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a human explicitly asks to reshape or annotate one pull request for review. Don't use for pushing the rewritten branch or mutating any remote.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a human explicitly asks to ship work through a clean branch and pull request. Don't use for force-pushing, reusing conflicting branches, or widening the change scope.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to propose an issue, file or open a bug report, or turn a reported defect into a tracked issue. Not for fixing the defect, triaging existing issues, or reviewing PRs.
日本語の概要は準備中です。原文の説明を表示しています。