メニュー
Capture bugs/enhancements/ideas to request-logs. For quick operations use /mc command instead.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Token-efficient tracking for AI orchestration. CLI-first for status updates (~50 tokens), agent fallback for complex ops (~1KB). Use when: updating task status, querying blockers, creating progress files, validating phases.
Use when changing artifact identity, versioning, manifests, search/matching, content resolution, repository interfaces, or the local/enterprise DB split in the SkillMeat codebase (skillmeat/core/, skillmeat/cache/, skillmeat/storage/, skillmeat/sources/) — i.e. the informal "Registry Core" kernel this AOS has not yet named as a literal module. Trigger keywords: registry core, artifact identity, repository interface, IArtifactRepository, ICollectionRepository, RepositoryFactory, cache.db, SKILLMEAT_EDITION, alembic multi-head, schema drift, cli_snapshot.json, deprecation window, backward compatibility, breaking change to core. Do NOT use for CLI-surface/agent-facing command routing (use `skillmeat-cli`), for BOM/attestation authoring (use `asdlc-skillbom-builder`), or for bundle/deployment-set packaging (use `asdlc-sam-artifact-packager`).
Use when packaging SkillMeat artifacts (skills, agents, commands, context entities, bundles, deployment sets, or project-starter templates) for deployment or distribution — creating a bundle (`skillmeat bundle create`/`add-member`), building and publishing a `.skillmeat-pack` round-trip (`bundle build-pack`/`publish-pack`/`export`/`import`), assembling a deployment set (`deployment-set create`/`add-member`/`deploy`), registering a project-starter scaffold template (`template create`), deploying a single artifact (`skillmeat add`, `skillmeat deploy`), or taking a safety snapshot before a risky change (`skillmeat snapshot`/`rollback`). Covers local-collection vs enterprise-edition packaging differences and post-deploy verification. Do NOT use for generating BOM/attestation provenance — use `asdlc-skillbom-builder` first. Do NOT use for pre-packaging quality review — use `asdlc-skill-review-board` first.
Use when an agent needs to produce SkillBOM provenance for skills, agents, commands, or other SkillMeat artifacts — generating a BOM snapshot (`skillmeat bom generate`), signing or verifying it with Ed25519 (`skillmeat bom sign|verify|keygen`), wiring git hooks that link commits to BOM state (`skillmeat bom hook install`), inspecting materialization sidecars for parameterized deploys (`skillmeat bom materializations`), or recording an owner-scoped attestation (`skillmeat attest create|list|show`). Covers exactly what fields a SkillBOM entry carries, how BOM ties into git history, and the honest gaps in promotion/approval status and policy enforcement. Do NOT use this skill for packaging artifacts into bundles/deployment-sets/templates — use `asdlc-sam-artifact-packager` instead. Do NOT use for pre-packaging quality review — use `asdlc-skill-review-board` first.
Answer CCDash project-intelligence questions using the shipped MCP tools when available and the in-repo `ccdash` CLI otherwise. Use when the operator or another agent asks about project status, feature forensics, workflow failure patterns, after-action reports, session intelligence (transcripts, search, detail), runtime validation posture, CLI timeout or caching behavior, container project onboarding, watcher binding, or how to troubleshoot the shipped CCDash API/worker/MCP surfaces. Keep routing aligned with the current shipped runtime contract and repo docs.
Audits CHANGELOG coverage for a git commit range; read-only — surfaces gaps for human remediation. Use this skill before a version bump, in CI, or ad-hoc to verify that all non-trivial commits are reflected in the changelog. Co-loaded with the release skill on every /release:bump invocation. Does not write or modify any files; outputs structured gap reports and exit codes only.
| name | meatycapture-capture |
| description | Capture bugs/enhancements/ideas to request-logs. For quick operations use /mc command instead. |
Request-log markdown files for development tracking.
| Scenario | Method | Tokens/Effort |
|---|---|---|
| Single capture during development | mc-quick.sh | ~50 tokens |
| AI agent capturing findings | mc-quick.sh | ~50 tokens |
| Batch capture (3+ items) | Direct CLI | ~200+ tokens |
| Complex notes or custom fields | Direct CLI | ~200+ tokens |
| Appending to existing docs | Direct CLI | ~150 tokens |
| Post-commit: update docs + close item | update-bug-docs.py | ~20 tokens |
| Batch file bugs (3+) from JSON/CSV | batch-file-bugs.sh | ~30 tokens |
Scripts spec: .claude/specs/script-usage/bug-automation-scripts.md
| Type | Strategy |
|---|---|
| bug | Daily aggregation - all bugs from same day in one doc titled "Bug Log - YYYY-MM-DD" |
| enhancement/idea/task/question | One doc per topic (title = request title, often 1 item) |
Ultra-simple wrapper - reduces ~20 lines JSON to single command:
mc-quick.sh TYPE DOMAIN SUBDOMAIN "Title" "Problem" "Goal" [notes...]
# Examples:
mc-quick.sh enhancement web deployments "Add remove button" "Button not implemented" "Full removal workflow"
mc-quick.sh bug api validation "Fix timeout" "Sessions expire early" "Extend TTL to 24h"
# With environment variables:
MC_PROJECT=other-project MC_PRIORITY=high mc-quick.sh bug cli commands "Title" "Problem" "Goal"
Environment Variables: MC_PROJECT (default: skillmeat), MC_PRIORITY (default: medium), MC_STATUS (default: triage)
Full documentation: ./usage-specs/mc-quick-script.md
/mc for simple operations)| Command | Example |
|---|---|
| List | meatycapture log list PROJECT --json |
| View | meatycapture log view PATH --json |
| Search | meatycapture log search "query" PROJECT --json |
| Capture | meatycapture log create --json < input.json |
| Note Add | meatycapture log note add DOC ITEM -c "text" |
| Update | meatycapture log item update DOC ITEM --status done |
| Action | When to Load |
|---|---|
| Capture | Batch capture, validation, templates |
| View/Search | Advanced filters, output formats |
| Status Update | Change item status, add notes |
| Projects | Configure projects, defaults |
See ./references/field-options.md for valid values.