Run any Skill in Manus with one click

issue-contract-expansion

Stars1

Forks0

UpdatedApril 5, 2026 at 09:28

Turn a concrete GitHub issue ask into repo-truth + implementation when the requirement is additive but the contract is not documented yet.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

aarshps

aarshps/hora-prathinidhi

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	issue-contract-expansion
description	Turn a concrete GitHub issue ask into repo-truth + implementation when the requirement is additive but the contract is not documented yet.

Issue Contract Expansion

When to Use

A GitHub issue asks for a concrete additive feature, surface, or workflow
Current repo docs do not yet describe the contract, but the ask is still landable
The session can update repo truth and the bounded implementation together

Canonical Surfaces

GitHub issue thread comments via ./.git/helpers/gh-app
AGENTS.md
README.md
The owner doc for the touched surface under docs/ or research/
The code or data files that implement the issue ask

Procedure

Read the full issue, latest comments, and the current owner doc for the affected surface
Decide whether the ask is additive and safe on current main, or whether it truly needs escalation
Use mapped only for brief decomposition, then move into active or writing once the path is clear
Update the owner doc, AGENTS.md, and any relevant skill in the same slice when repo truth is missing
Land the bounded implementation that matches the new repo truth; keep docs, code, and data aligned
Use validation-ready and closeout only after the shipped result rechecks clean on current main

Guardrails

Missing contract text alone is not a blocker
Reserve blocked for external dependencies, unsafe ambiguity, or a direct policy conflict that cannot be resolved in the same slice
Do not ship placeholder UI, synthetic data, or screenshot-only hacks just to avoid saying no
Keep issue comments concrete and user-surface-focused

Validation

The same slice updates repo truth and the implementing files
The issue thread reflects active or writing, not a blocker-only note, when the ask is additive
Closeout uses .agents/skills/issue-watch-closeout/SKILL.md after the result ships

More from this repository

same repository

data-validation

aarshps/hora-prathinidhi

Validate integrity of all public/data JSON files. Use when: after editing candidates, constituencies, or districts JSON; before committing data changes; checking coverage completeness; debugging data mismatches.

2026-04-251

public-candidate-sync

aarshps/hora-prathinidhi

Refresh public district candidate rows from structured live-field research plus staged facts/timelines. Use when: surfacing all candidates per constituency in the app, resyncing public/data after research candidate changes, or restoring legacy candidate route aliases.

2026-04-251

session-wrap-up

aarshps/hora-prathinidhi

Wrap up a meaningful repo work session. Use when: folding durable learnings into repo-local skills, syncing AGENTS/README/handoff docs, or preparing the final close-out commit and push.

2026-04-241

issue-watch-closeout

aarshps/hora-prathinidhi

Drive recurring GitHub issue work from shipped slices to final closeout or reusable closed-issue audits.

2026-04-241

constituency-outcome-slice

aarshps/hora-prathinidhi

Work one bounded constituency possible-outcome slice. Use when: creating or reviewing seat-local outcome packets under the new 1 primary + 3 reviewer workflow.

2026-04-081

ui-conventions

aarshps/hora-prathinidhi

UI rules for the Kerala elections app. Use when: modifying components, adding status indicators, changing how candidates or constituencies display, or touching motion.

2026-04-071

name	issue-contract-expansion
description	Turn a concrete GitHub issue ask into repo-truth + implementation when the requirement is additive but the contract is not documented yet.

Issue Contract Expansion

When to Use

A GitHub issue asks for a concrete additive feature, surface, or workflow
Current repo docs do not yet describe the contract, but the ask is still landable
The session can update repo truth and the bounded implementation together

Canonical Surfaces

GitHub issue thread comments via ./.git/helpers/gh-app
AGENTS.md
README.md
The owner doc for the touched surface under docs/ or research/
The code or data files that implement the issue ask

Procedure

Read the full issue, latest comments, and the current owner doc for the affected surface
Decide whether the ask is additive and safe on current main, or whether it truly needs escalation
Use mapped only for brief decomposition, then move into active or writing once the path is clear
Update the owner doc, AGENTS.md, and any relevant skill in the same slice when repo truth is missing
Land the bounded implementation that matches the new repo truth; keep docs, code, and data aligned
Use validation-ready and closeout only after the shipped result rechecks clean on current main

Guardrails

Missing contract text alone is not a blocker
Reserve blocked for external dependencies, unsafe ambiguity, or a direct policy conflict that cannot be resolved in the same slice
Do not ship placeholder UI, synthetic data, or screenshot-only hacks just to avoid saying no
Keep issue comments concrete and user-surface-focused

Validation

The same slice updates repo truth and the implementing files
The issue thread reflects active or writing, not a blocker-only note, when the ask is additive
Closeout uses .agents/skills/issue-watch-closeout/SKILL.md after the result ships