Skip to content

feat: CODEOWNERS 팀원 등록 및 이슈 생성 시 assignee 자동 할당 #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hamxxn merged 2 commits into from
Aug 7, 2026
Merged

feat: CODEOWNERS 팀원 등록 및 이슈 생성 시 assignee 자동 할당 #13

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7fa4eef
feat: CODEOWNERS 팀원 등록 및 to-spec 이슈 생성 시 assignee 자동 할당
thwjddlqslek Aug 6, 2026
cb08309
docs: 이슈 제목 접두사·완료 조건 컨벤션 명시
thwjddlqslek Aug 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude/skills/to-spec/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ The issue tracker and triage label vocabulary should have been provided to you

Check with the user that these seams match their expectations.

3. Write the spec using the template in [`.github/ISSUE_TEMPLATE/spec.md`](../../../.github/ISSUE_TEMPLATE/spec.md), then publish it to the project issue tracker. Apply the `ready-for-agent` label (already set as the template's default), plus exactly one type label: `bug` if this is a fix, `enhancement` otherwise. `/start-work` reads this label to pick the `fix/issue-{n}` vs `feat/issue-{n}` branch prefix, so every issue needs one.
3. Write the spec using the template in [`.github/ISSUE_TEMPLATE/spec.md`](../../../.github/ISSUE_TEMPLATE/spec.md), then publish it to the project issue tracker. Apply the `ready-for-agent` label (already set as the template's default), plus exactly one type label: `bug` if this is a fix, `enhancement` otherwise. `/start-work` reads this label to pick the `fix/issue-{n}` vs `feat/issue-{n}` branch prefix, so every issue needs one. Always include `--assignee @me` so the author is automatically assigned to the issue.

Fill each section from what was actually discussed - don't pad a section just to fill it:

Expand Down
5 changes: 1 addition & 4 deletions .github/CODEOWNERS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1 @@
# TODO: 실제 프로젝트 팀원의 GitHub 아이디로 교체할 것.
# PR 작성자는 자동으로 리뷰 요청 대상에서 제외되고, 나머지 팀원에게 리뷰가 요청된다.
#
# 예: * @teammate1 @teammate2 @teammate3
* @thwjddlqslek @sohxxny @hamxxn
2 changes: 2 additions & 0 deletions docs/agents/issue-tracker.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,8 @@ Issues and PRDs for this repo live as GitHub issues. Use the `gh` CLI for all op
## Conventions

- **Create an issue**: `gh issue create --title "..." --body "..."`. Use a heredoc for multi-line bodies.
- **Title**: prefix with `feat:`, `fix:`, or `chore:` (docs/tooling/maintenance work with no user-facing behavior change). `chore:` still gets the `enhancement` label and a `feat/issue-{n}` branch — there's no separate GitHub label or branch prefix for it. This prefix is for the issue/branch only — PR titles are free-form (`/ship`) since a PR can span multiple issues or conventions (e.g. `hotfix:`).
- **Acceptance criteria**: if the task touches source code, include both `pnpm typecheck` and `pnpm lint` passing — not just one.
- **Read an issue**: `gh issue view <number> --comments`, filtering comments by `jq` and also fetching labels.
- **List issues**: `gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'` with appropriate `--label` and `--state` filters.
- **Comment on an issue**: `gh issue comment <number> --body "..."`
Expand Down
Loading