메뉴
Append an accomplishment, framed as impact, to the Anytype page titled "Impact Log" for perf reviews and promo packets. Use when: logging an accomplishment, updating the impact log, recording impact, capturing what I shipped this week.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | impact-log |
| description | Append an accomplishment, framed as impact, to the Anytype page titled "Impact Log" for perf reviews and promo packets. Use when: logging an accomplishment, updating the impact log, recording impact, capturing what I shipped this week. |
| argument-hint | A short description of what was accomplished (optional; if omitted, derived from recent merged PRs / git history) |
Append a dated, impact-framed entry to the Anytype page titled Impact Log.
Requires an Anytype MCP server (e.g. anyproto/anytype-mcp). If no Anytype MCP tools are available, stop and tell the user to configure the server first — do not fall back to a local file.
gh search prs --author="@me" --state=merged --sort=updated --order=desc --limit=50 to find recently merged PRs. If that fails, try gh pr list --author="@me" --state=merged --limit=50.git log --author is a weak fallback only if gh is unavailable AND Claude happens to be inside a relevant repo — don't rely on it (e.g. when running from a top-level folder like ~/dev that isn't itself a git repo).If
gh search prsdoesn't support a--merged-afterflag on the installed version, filter by checking dates in the output.
Lead with the outcome, not the task. Capture, where known:
"Cut checkout p95 latency 40% by reworking the discount lookup (PROJ-812)" beats "worked on checkout performance."
Using the Anytype MCP tools (names below are the anyproto server's; if the configured server differs, discover the equivalents from the tool list):
get_spaces — select the space named "Knowledge Base". If it isn't found, ask which space to use rather than guessing.search_space within that space for an object named "Impact Log". Match exactly; if multiple match, ask. If none exists, tell the user and offer to create it with create_object.get_object_content (or export_object to markdown) to read the current body.The API has no append-a-block primitive, so append by rewriting the markdown body: take the current content, add the new entry under a ## <Month Year> heading (create the heading if this is the first entry of the month), and write the full updated body back with update_object (PATCH /v1/spaces/:space_id/objects/:object_id). Preserve all existing content — never reorder or drop prior entries.
## June 2026
- 2026-06-11 — <impact-framed entry> [PR/ticket link]
Confirm what was appended and to which space/page.
Scaffold a web repo with pnpm, Astro, and astro-bulma — plus Drizzle when the site needs a database — including package.json scripts for build/lint/test/fmt (and db:migrate when db-backed). Use when: setting up a new Astro project, scaffolding a web repo, initializing the standard web stack. Building block for create-website.
Add a GitHub Actions CI workflow running build, lint, test, and fmt checks with pnpm. Use when: adding CI, setting up GitHub Actions checks, adding a build/lint/test workflow. Building block for create-website.
Create a new website end-to-end: Astro repo with pnpm/astro-bulma; GitHub Pages for static sites, or Turso + Fly.io when the site needs a database; GitHub Actions for CI and deploy. Use when: creating a new website, spinning up a new web project, new site, scaffolding a static or full-stack Astro project.
Create a new app on Fly.io for the current project without deploying it, generating fly.toml and a Dockerfile. Use when: creating a Fly.io app, setting up Fly hosting, fly launch. Building block for create-website.
Add a GitHub Actions workflow that builds a static site and deploys it to GitHub Pages, with an optional custom domain. Use when: deploying a static site, GitHub Pages hosting, static site with a custom domain. Building block for create-website.
Add a GitHub Actions workflow that deploys to Fly.io on merge to main, with db migrations run as a Fly release_command. Use when: adding a deploy workflow, deploying on merge, setting up continuous deployment to Fly.io. Building block for create-website.