impl-gh-issue

A workflow for implementing a GitHub issue, which is a tracked software task or problem, from start to finish. It retrieves the issue, follows the project's rules, updates tests and documentation, and opens a pull request.

In plain words
What is it for?
It helps build features or fixes from issue numbers or URLs, using the project's design documents and adding the related tests and documentation.
Why use it?
It turns an issue description into a consistent implementation process tied to the project's architecture and conventions.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/bablsoft/accessflow/impl-gh-issue
Any agent
npx skills add bablsoft/accessflow --skill impl-gh-issue
Clone the repo
git clone --depth 1 https://github.com/bablsoft/accessflow

Made for: Claude Code, Codex.

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,384 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00049 $0.03384
Opus 5 $0.00024 $0.01692
Sonnet 5 $0.00010 $0.00677
Haiku 4.5 $0.00005 $0.00338

Measured 2d ago against content hash 2c4c6ccad0f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

impl-gh-issue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/impl-gh-issue/SKILL.md · 156 lines

How it starts

The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement a GitHub issue for AccessFlow

You are implementing a GitHub issue in the AccessFlow repo. CLAUDE.md is the authoritative rulebook — re-read it before writing code. This skill only adds a workflow on top.

Inputs

The user passes one of:

  • An issue number: 42, AF-58, FE-10
  • A full URL: https://github.com/bablsoft/accessflow/issues/42

Resolve the numeric issue with gh issue view <n> --json number,title,body,labels,assignees,url,state.

Project map

  • Docs (authoritative design):
    • docs/01-overview.md — product scope, goals, non-goals
    • docs/02-architecture.md — system architecture and request flow
    • docs/03-data-model.md — entities, columns, enums, indexes
    • docs/04-api-spec.md — REST + WebSocket spec (update before adding endpoints)
    • docs/05-backend.md — proxy engine, workflow state machine, AI analyzer, scheduled jobs
    • docs/06-frontend.md — directory layout, routing, state management
    • docs/07-security.md — auth, authorization matrix, encryption rules
    • docs/08-notifications.md — event types, channel configs, signed payloads
    • docs/09-deployment.md — Docker Compose, Helm, env-var reference
    • docs/10-editions.md — Community vs Enterprise feature matrix
    • docs/11-development.md — coding standards, testing strategy, Git workflow
    • docs/12-roadmap.md — milestone scope
  • Backend at backend/ — Java 25, Spring Boot 4, Spring Modulith. Modules under com.bablsoft.accessflow.{core,proxy,workflow,ai,security,notifications,audit}. Build: mvn verify (run from backend/ — there is no Maven wrapper).
  • Frontend at frontend/ — React 19 + Vite + TS + Ant Design 6 + TanStack Query + Zustand. Build: npm run lint && npm run typecheck && npm run test:coverage && npm run build.
  • End-to-end at e2e/ — Playwright suite with its own docker-compose.e2e.yml that builds backend + frontend from the working tree and seeds a deterministic admin via the bootstrap module. Owns auth and (over time) all critical user flows. Run: cd e2e && npm ci && npx playwright install --with-deps chromium && npm run stack:up && npm test.
  • Website at website/ — public marketing site, static HTML/CSS/JS, no build step. Edits land directly in HTML.
    • website/index.html — landing page (pitch, supported databases, AI providers, auth methods, feature list, roadmap, quick-start commands, tech stack, docs chapter list, top-level URLs).
    • website/docs/index.html — public user documentation page (deployment instructions, configuration entities — Review Plans, AI configs, datasources, OAuth, SAML, SMTP, notification channels, user creation — RBAC role matrix, operator-facing env vars).
    • website/README.md — content-source map describing which app/docs/ sections each website section is derived from; keep in sync when adding new website sections.
  • README at the repo root — public-facing project overview and quick start. Keep in sync when changes affect setup, tech stack, features, project structure, or top-level documentation.

Read the full file on GitHub · 156 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 156 lines · 49 tokens per session scan A 2c4c6ccad0f8

Subscribe to this mod's changes

impl-gh-issue is a skill published in the GitHub repository bablsoft/accessflow (4 stars, last pushed 2d ago), licensed Apache-2.0. It adds 49 tokens to every session and 3,384 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

hr-change-management

Help HR leaders, change managers, and business partners design, lead, and sustain organizational change initiatives. Use when asked to design a change management plan, advise leadership on change communication, build a stakeholder engagement strategy, create a change readiness assessment, design training and…

tuanductran/hr-skills · 80 tokens

workflow-automation

Design human-in-the-loop workflow orchestration for securities operations: task routing, approval chains, and SLA monitoring. Use when building multi-level approval chains with dollar thresholds and delegation of authority, enforcing four-eyes (maker-checker) controls, defining escalation rules for aging work items…

JoelLewis/finance_skills · 143 tokens

hr-consulting

Help HR business partners, HR leaders, and internal HR consultants advise business stakeholders, diagnose people problems, build business cases, and deliver strategic HR consulting engagements. Use when asked to advise a business leader on a people issue, build an HR business case, consult on an org problem, run an HR…

tuanductran/hr-skills · 74 tokens

hr-crisis-management

Help HR and business leaders plan for and respond to workforce crises — layoffs handled poorly, safety incidents, natural disasters, leadership scandals, or sudden business disruption. Use when asked to build a crisis response plan for HR, respond to a workplace incident, communicate during a crisis, plan for business…

tuanductran/hr-skills · 76 tokens

hr-ar-vr

Help HR and recruiting teams hire and assess AR/VR (augmented and virtual reality) engineering and design candidates. Use when asked to write an AR/VR engineer job description, create a spatial computing interview, assess an AR/VR candidates portfolio, build an AR/VR role leveling framework, or similar AR/VR hiring…

tuanductran/hr-skills · 72 tokens

hr-audit

Help HR and compliance teams plan and conduct HR audits, including policy compliance reviews, I-9/documentation audits, pay equity checks, and process audits. Use when asked to conduct an HR audit, audit HR compliance, review personnel files for compliance, build an HR audit checklist, or similar HR audit tasks.

tuanductran/hr-skills · 66 tokens