poko8nada/issue
.cursor/skills/issue/SKILL.md
Manages GitHub Issues using gh CLI — creation, decomposition, update, and close. Load when asked to create a new issue, break down a large task into issues, update issue status or labels, or close an issue after a PR is merged. Human decides whether to create an issue. Agent handles all gh CLI operations.
tools
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add poko8nada/corp_site-type01 issueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 1:26 AM4.1s1 file scanned
SKILL.md
- name:
- issue
- description:
- >
Issue Management
Principle
- 1 Issue = 1 PR — scope each issue to what can be completed in a single PR
- Human decides whether to create. Agent handles creation, updates, and closing.
- Issues are the session-to-session bridge — always reference the issue number in commits and PRs
- If implementation depends on fixed contracts or planned files, create or update the ADR first and link it from the issue
Granularity Guide
Good scope (1 PR完結)
- Add a specific feature function with tests
- Fix a specific bug
- Refactor a specific module
Too large — decompose first
- "Implement authentication" → break into: session management, login flow, token refresh, etc.
- "Redesign dashboard" → break into individual components or data-fetching concerns
When asked to implement something large, list the decomposed Issues for human approval before creating them.
Commands
Create
# Single issue
gh issue create \
--title "[concise action-oriented title]" \
--body "[context, acceptance criteria, references]" \
--label "[label]" \
--assignee "@me"
# Decompose a large task — list first, then create after approval
gh issue create --title "..." --body "..." --assignee "@me"
gh issue create --title "..." --body "..." --assignee "@me"
View & List
gh issue list --state open --assignee "@me"
gh issue view [number]
Update
gh issue edit [number] --title "..." --body "..."
gh issue edit [number] --add-label "in-progress" --remove-label "todo"
Close
# Close when PR is merged
gh issue close [number] --comment "Resolved in PR #[pr-number]"
Issue Body Format
## Context
[Why this needs to be done]
## Acceptance Criteria
- [ ] [specific verifiable condition]
- [ ] [specific verifiable condition]
## References
- Related: #[issue-number]
- ADR: docs/adr/NNNN-\*.md (if applicable)
- Behavior: docs/behavior.md (if behavior mapping changed)
Labels Convention
| Label | Meaning |
| ---------- | ----------------------------------- |
| bug | Something is broken |
| feature | New capability |
| refactor | Code change with no behavior change |
| docs | Documentation only |
| chore | Tooling, config, dependencies |
Commit & PR convention
Always reference the issue:
# Commit
git commit -m "feat: add [feature] (#[issue-number])"
# PR — closes issue automatically on merge
gh pr create \
--title "feat: [title] (#[issue-number])" \
--body "Closes #[issue-number]"
Related Skills
poko8nada/project-doc-bootstrap
development
VerifiedTrustedCommunity
Bootstraps project documentation for an existing repository by reading the codebase, README, tests, and package metadata, then creates or updates docs/overview.md, docs/behavior.md, and ADRs when significant architectural decisions are discovered. Use when asked to document a repo, extract project purpose, write overview/behavior docs, review an existing codebase, or capture architecture decisions from source.
SKILL.mdUpdated Apr 16, 2026
poko8nada/overview
development
VerifiedTrustedCommunity
Creates or updates docs/overview.md — the project's purpose and background. Load when starting a new project, when the project's goals or context have changed, or when docs/overview.md does not exist. Covers what to write, what to omit, and how to keep the document agent-friendly.
SKILL.mdUpdated Apr 16, 2026
poko8nada/new-feature
documentation
VerifiedTrustedCommunity
Implements a new feature using docs-first delivery, boundary-driven structure, and skeleton-first execution. Load when adding a route, feature, or new user-visible behavior.
SKILL.mdUpdated Apr 16, 2026
poko8nada/grill-me
development
VerifiedTrustedCommunity
When creating or refining ideas, ask the user detailed questions until a shared understanding is reached, and work through each branch of the decision tree one by one. Use this approach if you want to be rigorously questioned about an idea, or if you’ve specifically asked to be “grill me.”.
SKILL.mdUpdated Apr 16, 2026