메뉴
Generate formatted HTML reports and publish them to uselink. Use when the user asks for a code review report, architecture overview, sprint summary, daily standup report, or any structured report they want shared via a link.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Agent skills for publishing engineering artifacts to uselink — repo summaries, PR digests, changelogs, API docs, onboarding guides, reports, and specs. Each skill gathers data, generates HTML, and publishes via the uselink CLI.
Scan backend controllers/routes, generate API documentation as HTML, and publish to uselink. Use when the user wants to share API docs with frontend devs, partners, or stakeholders who need to understand the API contract.
Generate a changelog or release notes from git history and publish to uselink. Use when the user wants to share release notes, a changelog between versions, or a 'what shipped this week' summary with stakeholders.
Scan a codebase and generate a new-developer onboarding guide as HTML, then publish to uselink. Use when the user wants to create a getting-started guide, onboard a new team member, or share 'how to work in this repo' docs.
Summarize a pull request as a stakeholder-friendly HTML page and publish to uselink. Use when the user wants to share PR changes with PMs, reviewers, or business stakeholders who don't read diffs.
Scan a GitHub repo (local or remote), generate an architecture overview as HTML, and publish to uselink. Use when the user wants to share a repo summary, architecture overview, or codebase tour with stakeholders who don't have repo access.
| name | uselink-report |
| description | Generate formatted HTML reports and publish them to uselink. Use when the user asks for a code review report, architecture overview, sprint summary, daily standup report, or any structured report they want shared via a link. |
| allowed-tools | ["Bash","Read","Write","Glob","Grep"] |
See
report-templates.mdfor HTML templates and per-report-type data gathering commands.
Before generating any report, verify:
which uselink must resolve. If not, tell the user to run npm install -g uselink.~/.uselink/config.json must exist with api_key. If not, tell the user to run uselink login in their terminal (interactive -- Claude cannot run it).Stop here if either check fails. The user must fix these.
| Type | Trigger phrases | Data sources |
|---|---|---|
| Code review | "review report", "code review summary" | git diff, file reads, grep |
| Architecture | "architecture report", "system overview" | Directory scan, key config files |
| Sprint/daily | "sprint report", "daily summary", "standup" | git log --since, gh pr list |
| Custom | Anything else that asks for a "report" | Conversation context, user instructions |
If the type is ambiguous, ask. Do not guess.
report-templates.md for that report type.report-templates.md. Write to /tmp/uselink-report-<type>-<timestamp>.html.uselink publish <file> --title "<Report Title>" --format html.--format html. Reports are HTML, not markdown.<Type> Report -- <Project> -- <Date>. Example: Code Review -- my-project -- 2026-05-25.YYYY-MM-DD.git log output, not guesses about what was worked on.uselink login is interactive. Claude cannot run it. If config is missing, tell the user to run it themselves and stop.<link> and <style> tags that reference external files. All styles go in style attributes or a single <style> block in <head>. See templates in report-templates.md.git diff --stat first to scope the work, then read only the files with meaningful changes.git log date formats matter. Use --format="%H|%an|%s|%ai" for parseable output. Do not rely on the default pretty format.