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

project-docs

Brings task.md, changelog.md, and files.md back in sync with what the code says shipped. Reads git history and the working tree, never memory, and refuses to log features it cannot see in source. Use when a feature or fix lands, when the user says "update the docs", "sync changelog", "update files.md", "@update", or when task.md and the code disagree.

インストール方法を見る

含まれるファイル(6)

  • SKILL.md5.3 KB
  • agents/openai.yaml91 B
  • assets/large-logo.png3.2 KB
  • assets/small-logo.svg1.2 KB
  • references/convex-detection.md3.6 KB
  • references/evidence-rules.md2.3 KB

SKILL.md(原文)

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

Project docs

Three files describe a project to the next person who opens it. Keep them true.

FileAnswers
task.mdWhat is planned, in flight, and done
changelog.mdWhat changed for users, by version and date
files.mdWhat each file is for

Truth comes from the repo, not from the conversation. If the diff does not show it, it did not ship.

Run the sync

  1. Find the root. git rev-parse --show-toplevel, or the workspace root without git.
  2. Collect evidence. git log --date=short -n 20, git status --short, git diff --stat, and for the current change git diff HEAD --stat or the staged diff. See references/evidence-rules.md for what counts.
  3. Read all three files as they are. Note the last logged date and the last completed task.
  4. Update each file. Rules below.
  5. Check idempotency. If nothing new landed since the last entry, change nothing and say so.
  6. Scan for secrets and personal data before saving. See the redaction section.
  7. Report in a few lines. Show the new changelog entry or say the docs were already current.

task.md

Sections: ## To Do, ## In Progress, ## Completed.

  • Move an item to Completed only if its verification step ran. If the PRD lists a check that has not run, leave it In Progress and say which check is pending.
  • Completed entries: - [x] YYYY-MM-DD HH:mm UTC <what>. <PRD path if any>. <files touched>. Verified: <command or outcome>.
  • Never delete history. Old completed items stay.
  • If task.md does not exist, create it with the three headings and the current change under Completed or In Progress based on the evidence.

changelog.md

Keep a Changelog format. ## [Unreleased] at the top, then ## [x.y.z] - YYYY-MM-DD blocks, each with ### Added, ### Changed, ### Fixed, ### Removed as needed.

  • Dates come from git log --date=short. The release date is the date of the commit that bumped the version, or today's UTC date if it has not been committed yet. Never a placeholder, never a future month.
  • Write for the user of the project, not the author. "Uploads over 5 MB now show a progress bar" beats "refactored upload hook".
  • One line per change. Group related commits.
  • Do not log dependency bumps, formatting, or generated files unless they change behavior.
  • If a version bump exists in package.json with no matching heading, add the heading.

files.md

One line per file that matters. Grouped by folder.

## convex/
- `schema.ts` tables and indexes
- `stats.ts` heartbeat mutation with 10s dedup window, page view inserts

## src/hooks/
- `usePageTracking.ts` sends heartbeats, debounced 5s, path change aware
  • Add every new source file from the diff.
  • Fix descriptions that the diff made wrong.
  • Skip node_modules, _generated, lockfiles, build output, and assets unless they are hand written.
  • Keep each description under one line. What it is for, not how it works.

Convex projects

When the repo has a convex/ folder, the changelog and files.md can name Convex features, but only ones the source proves. references/convex-detection.md lists what file shows what.

Short version:

  • A component counts only if convex/convex.config.ts registers it. A dependency in package.json is not proof.
  • Crons count only if convex/crons.ts exists and registers a job.
  • HTTP actions count only if convex/http.ts has a route.
  • Auth counts only if convex/auth.config.ts or an auth component is present.
  • AI model names count only if code or config names them. Do not guess which model built the app.

Prefer none over an invented value.

Redaction

changelog.md and files.md are often public. Treat them that way.

  • Never open .env, .env.local, or any secret store to fill in a doc. Env var names are fine to mention. Values never.
  • Never include API keys, tokens, email addresses, phone numbers, street addresses, private hostnames, or application data records.
  • Scan the whole file before saving, not just the new lines. Replace any address shaped text with [redacted] and say so in one line.
  • Log behavior, not identifiers. "Signed webhook verification for inbound mail" is fine. The inbox address is not.

Boundaries

  • Edit only task.md, changelog.md, files.md, and PRDs the user points at. Nothing else unless asked.
  • Never commit, push, deploy, publish, or tag. Print the suggested commit message instead.
  • Never rewrite older entries for tone. Fix facts when the evidence contradicts them and flag the correction.
  • Do not call production APIs or query live data to make the docs richer.

Report format

Synced project docs.

changelog.md  added 2.1.0 (2026-09-15): 3 added, 1 fixed
files.md      added 2 files, updated 1 description
task.md       moved 1 item to Completed, 1 still In Progress (verification pending: e2e)

Suggested commit: docs: sync changelog, files, and tasks for 2.1.0

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Keeps a change scoped to what was asked. Flags extra features, refactors, and 'while we are here' edits, and moves them to a suggestions list instead of the diff. Use when a request is small and the agent is about to expand it, when a PRD grows beyond its problem statement, or when the user says 'just do what I asked'.

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

waynesutton/builder-skills4062026年9月28日 更新

convex

無料

Routes Convex work to the right builder skill and covers the handful of rules that apply everywhere: validators on every function, withIndex over filter, idempotent mutations, internal functions for scheduling. Use when a task mentions Convex and no more specific skill matches, or as the first stop before picking one.

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

waynesutton/builder-skills4062026年9月28日 更新

Builds AI agents on the Convex agent component: threads, messages, tools that call queries and mutations, streaming, RAG with vector search, and workflows for multi step jobs. Use when adding a chat assistant, tool calling agent, or retrieval feature to a Convex app.

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

waynesutton/builder-skills4062026年9月28日 更新

Production patterns for Convex apps and the rules the @convex-dev/eslint-plugin enforces: validators, indexes, idempotent mutations, avoiding OCC conflicts, thin function wrappers, error handling. Use when reviewing Convex code, asking whether a pattern is right, setting up ESLint, or fixing write conflicts and slow queries.

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

waynesutton/builder-skills4062026年9月28日 更新

Creates reusable Convex components with defineComponent, a clean client wrapper, their own schema, and an npm publish setup. Use when extracting a feature into a package, building something for the Convex component directory, or when a component's functions are not showing up in the parent app.

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

waynesutton/builder-skills4062026年9月28日 更新

Schedules work in Convex: cron jobs in convex/crons.ts, one off scheduled functions with runAfter and runAt, batching large jobs, and cancelling or inspecting the queue. Use when something needs to run on a timer, later, or in the background, or when a cron is not firing.

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

waynesutton/builder-skills4062026年9月28日 更新

waynesutton のスキルをすべて見る

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