syntaqxAgents are told how a commit closes an issue: on flagon-io/g1t #47 the billing session pushed its work straight to main with commits ending "(#47)", which only links the issue, so #47 stayed open after it shipped and was closed by hand. The plugin's SessionStart and subagent context (TRAILER in hooks/g1t.mjs), the work-on-issue skill's Finish step, the system prompt of sessions on Claude Managed Agents (for a repository's first commit) and the MCP server's instructions now say that a pull request's merge closes its issue, and a commit pushed straight to the default branch closes one only when its message says Closes #N (Fixes, Resolves), never with a bare (#N); the MCP instructions add that issue close with commit closes one after the fact. The Claude Code plugin guide says so. Deploy: api and integrations; the plugin ships with its next release. Checked: node --test of plugins/claude-code/test (56), cargo test -p g1t-api mcp (5), cargo test -p g1t-integrations agent_sessions (11).047ae5fHistory
- ..
- notify
- repo
- settings
- workspace
- auth-github-callback.tsx
- auth-github-username.tsx
- auth-github.ts
- avatar-user.ts
- confirm-email.tsx
- desktop-runner.ts
- device.tsx
- download.tsx
- downloads-runner.ts
- explore.tsx
- forgot.tsx
- github-install.ts
- github-setup.tsx
- home.tsx
- hovercard-user.ts
- inbox-json.ts
- inbox-moved.ts
- install-script.ts
- invitations.tsx
- invite.tsx
- login-two-factor.tsx
- login.tsx
- logout.tsx
- new-github.tsx
- new.tsx
- not-found.tsx
- notifications.tsx
- oauth-authorize.tsx
- people-json.ts
- policies.tsx
- policy.tsx
- pricing.tsx
- register.tsx
- reset.tsx
- robots-txt.ts
- search-json.ts
- search.tsx
- security-txt.ts
- security.tsx
- settings-menu-json.ts
- sitemap-xml.ts
- status-json.ts
- status.tsx
- support.tsx
- user.tsx
- verify.tsx
- well-known-g1t.ts