diff options
Diffstat (limited to 'modules/development/pi-coding-agent/prompts')
8 files changed, 190 insertions, 0 deletions
diff --git a/modules/development/pi-coding-agent/prompts/debug.md b/modules/development/pi-coding-agent/prompts/debug.md new file mode 100644 index 0000000..19aafb4 --- /dev/null +++ b/modules/development/pi-coding-agent/prompts/debug.md @@ -0,0 +1,23 @@ +# Debug + +Investigate the reported problem and determine its root cause before making changes. + +## Instructions + +1. Understand the reported symptom. +2. Inspect the relevant implementation and configuration. +3. Reproduce the failure when practical. +4. Collect evidence from errors, logs, state, and behavior. +5. Form concrete hypotheses. +6. Test the hypotheses systematically. +7. Identify the most likely root cause. +8. Make the smallest appropriate fix. +9. Run targeted validation and regression tests. + +## Rules + +- Do not guess when evidence can be collected. +- Do not make unrelated changes. +- Distinguish symptoms from root causes. +- Preserve existing user changes. +- Report what was reproduced, what was tested, and what remains uncertain.
\ No newline at end of file diff --git a/modules/development/pi-coding-agent/prompts/explain.md b/modules/development/pi-coding-agent/prompts/explain.md new file mode 100644 index 0000000..ca54ceb --- /dev/null +++ b/modules/development/pi-coding-agent/prompts/explain.md @@ -0,0 +1,14 @@ +# Explain + +Explain the requested code, behavior, architecture, or concept using the actual project as context. + +## Instructions + +- Inspect the relevant code before explaining it. +- Start with the highest-level purpose. +- Trace the relevant flow or relationships. +- Reference concrete files, functions, classes, modules, or commands where useful. +- Explain important design decisions and dependencies. +- Distinguish clearly between observed behavior and inference. +- Do not propose changes unless explicitly asked. +- Prefer a concise explanation first, followed by deeper detail when useful.
\ No newline at end of file diff --git a/modules/development/pi-coding-agent/prompts/implement.md b/modules/development/pi-coding-agent/prompts/implement.md new file mode 100644 index 0000000..2249c53 --- /dev/null +++ b/modules/development/pi-coding-agent/prompts/implement.md @@ -0,0 +1,26 @@ +# Implement + +Implement the requested change in the existing project. + +## Instructions + +- Inspect the relevant project structure and existing implementation first. +- Read applicable project-local instructions. +- Understand the surrounding code before editing. +- Follow existing conventions and architecture. +- Prefer the smallest correct implementation. +- Reuse existing functionality where appropriate. +- Avoid unrelated refactoring. +- Preserve user changes. +- Add or update tests when appropriate. +- Run the most relevant formatter, linter, type checker, build, or test commands after making changes. + +## Before finishing + +Report: + +- what was changed +- what was validated +- any remaining limitations or failures + +Do not claim validation that was not actually performed.
\ No newline at end of file diff --git a/modules/development/pi-coding-agent/prompts/investigate.md b/modules/development/pi-coding-agent/prompts/investigate.md new file mode 100644 index 0000000..a662a18 --- /dev/null +++ b/modules/development/pi-coding-agent/prompts/investigate.md @@ -0,0 +1,25 @@ +# Investigate + +Investigate an unfamiliar part of a repository or a technical problem and return a factual report without modifying files. + +## Instructions + +- Inspect the relevant repository structure first. +- Follow references and dependencies as necessary. +- Identify the important files, components, and entry points. +- Determine how the relevant functionality currently works. +- Look for existing documentation, tests, configuration, and related implementations. +- Use authoritative external documentation when required. +- Separate verified facts from assumptions or hypotheses. +- Do not make changes. + +## Output + +Return: + +- what was investigated +- what was found +- relevant files and locations +- important dependencies or relationships +- unresolved questions +- recommended next investigative or implementation step, when appropriate
\ No newline at end of file diff --git a/modules/development/pi-coding-agent/prompts/plan.md b/modules/development/pi-coding-agent/prompts/plan.md new file mode 100644 index 0000000..2422059 --- /dev/null +++ b/modules/development/pi-coding-agent/prompts/plan.md @@ -0,0 +1,25 @@ +# Plan + +Create an implementation plan for the requested change without modifying files. + +## Instructions + +- Inspect the repository and relevant code first. +- Identify existing architecture, conventions, and constraints. +- Determine the smallest practical set of changes. +- Break the work into ordered, independently understandable steps. +- Identify files or components likely to change. +- Identify important dependencies and risks. +- Identify how the completed work should be validated. + +## Output + +Provide: + +1. A concise summary of the intended change. +2. The proposed implementation steps. +3. Relevant files/components. +4. Important risks or open questions. +5. A validation strategy. + +Do not invent implementation details that have not been established by inspecting the project.
\ No newline at end of file diff --git a/modules/development/pi-coding-agent/prompts/refactor.md b/modules/development/pi-coding-agent/prompts/refactor.md new file mode 100644 index 0000000..a5b38ad --- /dev/null +++ b/modules/development/pi-coding-agent/prompts/refactor.md @@ -0,0 +1,24 @@ +# Refactor + +Improve the structure, readability, or maintainability of existing code while preserving behavior unless a behavior change is explicitly requested. + +## Instructions + +- Inspect the existing implementation before proposing changes. +- Identify the concrete problem the refactor should solve. +- Preserve public behavior and interfaces unless explicitly required otherwise. +- Prefer small, understandable transformations. +- Follow existing project conventions. +- Avoid introducing abstractions without a clear benefit. +- Avoid unrelated cleanup. +- Update affected tests when necessary. +- Run relevant validation after the refactor. + +## Before finishing + +Verify that: + +- intended behavior is preserved +- tests still pass or have been appropriately updated +- no unnecessary dependencies or abstractions were introduced +- the resulting code is simpler or clearer than before
\ No newline at end of file diff --git a/modules/development/pi-coding-agent/prompts/review.md b/modules/development/pi-coding-agent/prompts/review.md new file mode 100644 index 0000000..57876f4 --- /dev/null +++ b/modules/development/pi-coding-agent/prompts/review.md @@ -0,0 +1,22 @@ +# Review + +Review the current changes for correctness, regressions, maintainability, and potential security issues. + +## Instructions + +- Inspect the working tree and relevant diff before reviewing. +- Understand surrounding code and existing conventions. +- Look for: + - correctness problems + - edge cases + - regressions + - error-handling problems + - security issues + - API or behavior compatibility problems + - missing or inadequate tests + - unnecessary complexity +- Prioritize concrete, actionable findings. +- Do not criticize style unless it materially affects maintainability or project conventions. +- Do not rewrite the code unless explicitly asked. +- Report findings with file and location references when possible. +- If no significant issues are found, say so and mention what was checked.
\ No newline at end of file diff --git a/modules/development/pi-coding-agent/prompts/summarize.md b/modules/development/pi-coding-agent/prompts/summarize.md new file mode 100644 index 0000000..a53b468 --- /dev/null +++ b/modules/development/pi-coding-agent/prompts/summarize.md @@ -0,0 +1,31 @@ +# Summarize + +Summarize the requested code, work session, change set, investigation, or repository state using the available evidence. + +## Instructions + +- Base the summary on inspected files, diffs, commands, and tool results. +- Preserve important technical details while removing unnecessary narrative. +- Distinguish completed work from planned or incomplete work. +- Mention important decisions, constraints, failures, and unresolved issues. +- Include file references when useful. + +## Preferred structure + +### Summary + +A concise overview. + +### Changes + +What was changed or discovered. + +### Validation + +What was tested or verified. + +### Outstanding + +What remains incomplete, uncertain, or requires follow-up. + +Do not invent missing information.
\ No newline at end of file |